Description: Memory spike from 200MB to 4 GB with some content on the clipboard Steps to Reproduce: 1. Open attachment 139120 [details] (ignore macro) 2. CTRL+A 3. CTRL+X 4. CTRL+Q & Dont'save -> Watch the spike in memory usage & slowness to close Actual Results: 4 GB mem usage slow close Expected Results: Seems excessive Reproducible: Always User Profile Reset: No Additional Info: Version: 7.0.0.0.alpha0+ (x64) Build ID: 4475bcd83aac7e033fc5250f268eb922bd471e7b CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win; Locale: en-US (nl_NL); UI-Language: en-US Calc: CL
Confirmed. After a while soffice closed and memory is released. In any case seems the file has direct formatting beyand data range make large the copy. Version: 7.0.0.0.alpha0+ (x64) Build ID: 4475bcd83aac7e033fc5250f268eb922bd471e7b CPU threads: 4; OS: Windows 10.0 Build 19603; UI render: Skia/Raster; VCL: win; Locale: es-ES (es_ES); UI-Language: en-US Calc: CL
for the Bug Hunting Session 7.0.0.0.a1+: no repro with above ver., program closes, mem is dropped, may be a very little amount is still blocked (one pixel width line in task manager), but that's covered in other bugs ... fu..ed ver. info as bugs answered normal save changes with a red banner: 'There is no version named '7.0.0.0.alpha0+ Master' in the 'LibreOffice' product.' but that ver. is! listed in the dropdown,
Still in Version: 7.0.0.0.alpha0+ (x64) Build ID: 97a2c1fc5e376c0c00968f17a0392c6d3a5ed565 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win; Locale: nl-NL (nl_NL); UI-Language: en-US Calc: threaded On CTRL+Q memory spikes.. 2GB.. takes some time to close.. drops to 0
Created attachment 160712 [details] mem usage with 6.2.8.2 and 7.0.0.0.a1+ @Telesto: still see no issue, also recheck with 6.2 is ok, see attached screenshot, 1: open file, ctrl-a, ctrl-x, ctrl-q, "don't save" with 6.2.8.2, 2: open file, ctrl-a, ctrl-x, ctrl-q, "don't save" with 7.0.0.0.a1+, maybe you linked to a wrong file? relative small, 48 kB, "Food Calendar.ods", mentioned somewhere as open before a crash? to boil down pls. provide screenshot of mem usage with file downloaded from link in OP, reg. b.
Created attachment 160713 [details] Screencast
impressive, re-checked, even with a writer doc in the background to keep soffice open, no spike, special win 8.1 problem? (i'm on 7)
(In reply to b. from comment #6) > special win 8.1 problem? (i'm on 7) See comment 1 -> Win 10
@b total off topic Hoping you will around when they are finished with allowing more than 1024 columns (bug 50916).. I'm already foreseeing problems. Undo/Redo/Memory usage
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
Can still verify 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 - - - The document took: 236 MB = On load After Step 4, quitting, it took: - ~39 seconds of constant CPU usage with the RAM usage wildly jumping between all numbers: - 4.4 GB - 3.3 GB - + it even jumped up to 7 GB (!!!) at one point. At the end of the 39 seconds, LO finally disappeared from Task Manager.
I re-reported the same issue a while back; oops. not a bug.. *** This bug has been marked as a duplicate of bug 159272 ***
Correcting duplicate to the open one, we don't use dupes of dupes. *** This bug has been marked as a duplicate of bug 112537 ***