Description: I've made a Reddit post on the LibreOffice subreddit with the same title as the summary of this bug report and I was directed to report it here. It happens when I open a PDF document that contains a 1200 dpi resolution scan and then LibreOffice Draw uses a lot of system Memory and is basically unusable with how slow it is and then it can stop responding. Steps to Reproduce: 1.Open a scanned PDF document where the scan resolution is 1200 dpi. 2.Once the file is open LibreOffice will use 1 GB of Memory. 3.If you try moving the image in the document it can jump to 2 GB. Actual Results: Basically unusable Expected Results: To be able to use LibreOffice Draw Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.0.4.2 (x64) Build ID: dcf040e67528d9187c66b2379df5ea4407429775 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded This was my first time using LibreOffice and I was trying out different documents that I usually open. I've been using Adobe Reader DC to open other documents scanned the same way and never experienced it. I'm going to attach a PDF with a blank paper cardboard scanned the same way that other documents that can cause the same problem. I'm using an ASUS X407UA (i3-8130U CPU and 4 GB RAM)
Created attachment 168832 [details] A PDF file that can cause the problem.
For me at opening 800 MB but after a few seconds 470 MB, moving the image grows again up to 800 MB, but again after a few seconds 470 MB. In any case 1200 dpi looks like a huge resolution, that has their cost to work with.
Thank you for reporting the bug. For Version: 7.2.0.0.alpha0+ (x64) opening file uses 670 MB and moving the image grows up to 1GB, but again after a few seconds drops to 670 MB. For Version: 7.0.3.1 (x64) opening file uses 1GB and moving the image grows up to 1.06 GB. I can not reproduce the bug in Version: 7.0.3.1 (x64) Build ID: d7547858d014d4cf69878db179d326fc3483e082 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL Version: 7.2.0.0.alpha0+ (x64) Build ID: 761a672d62df1891b9f4f367a499b220ab2b33fa CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL
(In reply to mulla.tasanim from comment #3) > Thank you for reporting the bug. > > For Version: 7.2.0.0.alpha0+ (x64) > opening file uses 670 MB and moving the image grows up to 1GB, but again > after a few seconds drops to 670 MB. > > For Version: 7.0.3.1 (x64) > opening file uses 1GB and moving the image grows up to 1.06 GB. > > I can not reproduce the bug in > > Version: 7.0.3.1 (x64) > Build ID: d7547858d014d4cf69878db179d326fc3483e082 > CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win > Locale: en-US (en_US); UI: en-US > Calc: CL > > Version: 7.2.0.0.alpha0+ (x64) > Build ID: 761a672d62df1891b9f4f367a499b220ab2b33fa > CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win > Locale: en-US (en_US); UI: en-US > Calc: CL Have you tried opening it in the version I used? Based on your testing the two different versions already have different ram use, so could switching to different version help me? I new to this LibreOffice so I don't really know what to do.
(In reply to m.a.riosv from comment #2) > For me at opening 800 MB but after a few seconds 470 MB, moving the image > grows again up to 800 MB, but again after a few seconds 470 MB. > > In any case 1200 dpi looks like a huge resolution, that has their cost to > work with. So it will have to be fixed by software optimization and/or just more powerful hardware to open it? Is there a way to set Draw to display the image of file to a lower resolution? Since dpi is usually just for printing.
Hi Proj, At first try I was able to replicate in: Version: 6.0.7.3 Build ID: 1:6.0.7-0ubuntu0.18.04.10 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); Calc: group But I could not replicate in: Version: 7.2.0.0.alpha0+ / LibreOffice Community Build ID: 3ec8981b4830d646ad73836d9819db4f8342b499 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-02-13_07:07:42 Calc: threaded Nor in: Version: 7.0.4.2 Build ID: dcf040e67528d9187c66b2379df5ea4407429775 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded I tested again in Version: 6.0.7.3 and could not replicate. Can you please retest in: Version: 7.1.0.3 / LibreOffice Community Build ID: f6099ecf3d29644b5008cc8f48f42f4a40986e4c on your OS of choice.
I downloaded and tested it on Version: 7.1.0.3 (x64) / LibreOffice Community Build ID: f6099ecf3d29644b5008cc8f48f42f4a40986e4c CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded I'm getting a stable ~750 MB of Memory usage. I no longer experience the issue even when I select the image the move it around, seems like something they changed for 7.1.0.3 has fixed whatever caused it on 7.0.4.2. With that said, do I change the status of this report?
[Automated Action] NeedInfo-To-Unconfirmed
Thanks for following up, we use worksforme, when we do not know what fixed it