Memory isn't freed. It will be 2,6 GB even after export finishes
Steps to Reproduce:
1. Open attachment 133491 [details]
2. Export to PDF
3. Notice that the memory usage is still 2,6 GB after export finishes
2,6 GB is used until the document is closed.
It isn't freed after PDF export finishes
User Profile Reset: No
Version: 126.96.36.199.alpha0+ (x64)
Build ID: 42a1a1c6b91907f81e15066ffab219411f18c4db
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: GL; VCL: win;
Locale: nl-NL (nl_NL); UI-Language: en-US
Version: 188.8.131.52 (x64)
CPU-Threads: 4; BS: Windows 10.0 Build 18363; UI-Render: Standard; VCL: win;
Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE
max: ~2,8 GB
Version 184.108.40.206 (Build ID: e183d5b)
max: ~ 1,4 GB
is used until the document is closed.
I can reproduce with the 6.2.8 version in Ubuntu 18.04 x64.
It is just a 1.4 MB draw file, but memory usage goes from 80 MB to 4.4 GB all the way up. After sucessful pdf export, the memory is not freed. Memory is freed when you close the application.
I also noticed that, when I export to PDF for the 2nd time, the memory remains 4.4 GB without any further increase at all. So, maybe the memory is retained intentionally after the 1st pdf export (to be used later)? If so, this is not the correct option, as no one is exporting the same file as pdf if he already exported it.
But anyway, there may be two issues in this: 1) a small 1.4 MB file should never use 4.4 GB memory in pdf export, and 2) after pdf export, the used memory should be freed up.
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
Version: 220.127.116.11.alpha0+ (x64) / LibreOffice Community
Build ID: 88d7aa8ab79b1197191b5eb24a3b67d313797026
CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Vulkan; VCL: win
Locale: ru-RU (ru_RU); UI: en-US
I noticed memory usage and still reproducable in LO 7.6 Dev alpha release.
Version: 18.104.22.168.alpha0+ (X86_64) / LibreOffice Community
Build ID: d887b6a6fa2a572f48498839c5a68791c3196634
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: en-IN (en_IN); UI: en-US