Description: Memory usage increasing from 133 to +/- 255 MB after scrolling down with page down Steps to Reproduce: The issue is fixed in the strict sense, when looking at file open. However the issue still present: 1. Open the attachment 145863 [details] 2. Wait until the memory drops to 133MB (fine) (since 30-10-2018; see bug 120735) 3. Now hold page down until the end, memory usage is back to 255 Actual Results: 255 MB memory usage Expected Results: Somewhere around the 133 MB Reproducible: Always User Profile Reset: Yes Additional Info: Version: 6.2.0.0.alpha1+ Build ID: 2e184378da6058af14acf208d6469fadf44d04ed CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2018-10-30_03:29:39 Locale: nl-NL (nl_NL); Calc: threaded
Not sure how to bibisected, it's obvious after the bugfix for bug 120735
Confirmed in bug 121059.
Dear Telesto, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Version: 7.2.2.1 (x64) / LibreOffice Community Build ID: 0e408af0b27894d652a87aa5f21fe17bf058124c CPU threads: 12; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: it-IT (it_IT); UI: it-IT Calc: threaded Actual Results: Scrolling the document down and up, memory usage increase rapidly. In my case I reached 326 MB. Reproducible: Always
Dear Telesto, 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! Warm Regards, QA Team MassPing-UntouchedBug
Retested in: Version: 24.2.0.3 (X86_64) / LibreOffice Community Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1 CPU threads: 8; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded - - - Followed the steps in Comment #0 exactly: ~538 MB on load ~480 MB while holding Page Down + constant ~20% CPU usage (on my 8 core CPU) while scrolling. The page loading was jerky/stuttery as it went through the pages... but besides that, my memory usage actually WENT DOWN while I was scrolling. When I: - held Page Up - made it back to Page 1 my RAM usage was: ~490 MB - - - I also tried Comment #4: > Scrolling the document down and up, memory usage increase rapidly. I was: 1. Holding Page Down for a while 2. Stop 3. Holding Page Up for a while 4. Stop 5. (Repeat Steps 1–4.) and I wouldn't call it "increasing rapidly". My RAM slowly rose ~1–4 MB per 50ish pages—I assume because LO was holding/loading nearby pages in memory—because as I went up/down: - the CPU dropped - Instead of ~20% while scrolling, it was ~12–15%. - + I was able to scroll through all those previous pages much more quickly. - LO was moving through pages MUCH faster/snappier. (Hence, why I think those pages/layouts/spellchecking-squigglies were now sitting more efficiently in memory.) So... it seems like this may have been squished somewhere along the line... at least for this specific document.
Thanks for testing. Bug 121059 was also closed, so let's go with WFM.