Within a few 'saves' of large Writer files, LO 5.3 memory use increases from ~200Mb up to 10Gb and necessitates repeated closing of LO. This has been a problem throughout use of LO 5+.
Hello, it seems you're using an old version of LibreOffice. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
There's definitely still a memory leak with 5.3.1. Each time I save the RAM grabbed by writer goes up. Also, I've noticed with recent versions that if I save, when there's nothing new to save, unlike older versions, it fails to spot this and still goes through the exercise of saving (and grabbing more RAM).
Hello, Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
I'm afraid it's not possible to remove confidential data; there's too much of it. However, are you saying that the leak is not systemic to LO? ie. it may be specific to my particular file? I've certainly found this happening with other large files. It is possible it happens with smaller ones but I guess it would happen at a slower rate so not be noticed before the next reboot.
Hello, If you're certain it happens with other large files, please attach one of those files which doesn't contain confidential data, otherwise, it's impossible for us to triage this issue.
Created attachment 133999 [details] Sample File 1. Open attached fie 2. Select All (CTRL+A) 3. Apply Bold formatting (CTRL+B) 4. Save file (CTRL+S) 5. With still everything selected: Apply Italic (CTRL+I) 6. Save file (CTRL+S) 7. With still everything selected: Apply Underline (CTRL+U) 8. Save file (CTRL+S) 9. With still everything selected: Apply RED font color 10. Close the document (back to start center) 11. Open the document again. Repeat steps Saving steps are not a hard requirement Other opinions with the same effect 1. Playing with default styles 2. Remove formatting all formatting 3. Superscript Every steps adding up to quite some memory usage. Only repeating steps above 2 or 3 times creates a memory usage of 500 mb. No repro on Windows.
Was able to repro. Went through recommended steps, closed, reopened, and repeated processes 3 times, initial memory when from about 238mb up to around 500mb. Performance was noticeably slower with each iteration to reproduce steps as well. Repro on: Version: 5.3.3.2 Build ID: 3d9a8b4b4e538a85e0782bd6c2d430bafe583448 CPU Threads: 4; OS Version: Mac OS X 10.11.6; UI Render: default; Layout Engine: new; Locale: en-US (en.UTF-8); Calc: group
Patrick, Yes, that sounds about right. And it's definitely a case of the LO being used, rather than the file simply being opened that takes the memory. Eg. I've just opened an 'offending file' and LO is using 175Mb, up from 54Mb when no file opened. However, if I start editing, will quickly rise to 1Gb and a 2nd file of similar size would go over 1.5Gb. I have also noticed that Writer takes considerable time just to react after moving to it from another application. Presumably it is having to grab RAM from other applications?
Repro with Version 4.4.7.2 but not with Version: 4.3.7.2 Build ID: 8a35821d8636a03b8bf4e15b48f59794652c68b
Also a repro on Linux (but not on Windows) Version: 5.4.1.2 Build ID: ea7cb86e6eeb2bf3a5af73a8f7777ac570321527 CPU threads: 1; OS: Linux 3.13; UI render: default; VCL: gtk2; Locale: en-US (en_US.UTF-8); Calc: group
(In reply to Telesto from comment #6) > Created attachment 133999 [details] > Sample File > > 1. Open attached fie > 2. Select All (CTRL+A) > 3. Apply Bold formatting (CTRL+B) > 4. Save file (CTRL+S) > 5. With still everything selected: Apply Italic (CTRL+I) > 6. Save file (CTRL+S) > 7. With still everything selected: Apply Underline (CTRL+U) > 8. Save file (CTRL+S) > 9. With still everything selected: Apply RED font color > 10. Close the document (back to start center) > 11. Open the document again. Repeat steps > > Saving steps are not a hard requirement > Other opinions with the same effect > 1. Playing with default styles > 2. Remove formatting all formatting > 3. Superscript > > Every steps adding up to quite some memory usage. Only repeating steps above > 2 or 3 times creates a memory usage of 500 mb. I did this cycle 3 times, after reopening doing Ctrl-A, Ctrl-M to remove formatting. I did not observe this "adding up to quite some mem usage". After the third closing, I thought "hmm, now it did not go down", but then after I opened it, the mem use dropped by 30 MB again. I think it would be worth it for everyone affected to re-test with master. If dusk can still repro the leak, we really need an example file. This increase of gigabytes is certainly something that should be instantly recognisable. Arch Linux 64-bit Version: 6.1.0.0.alpha1+ Build ID: eeaf6dee2d278eaa037d95a756ad0ffab3314bc2 CPU threads: 8; OS: Linux 4.16; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on May 24th 2018
@Dusk Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear dusk@gotadsl.co.uk, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear dusk@gotadsl.co.uk, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp