Description: Memory usage is heavily increasing on every table formatting style switch (large table) Steps to Reproduce: 1. Open the attached file 2. Open a process monitor tool 3. Place the cursor in the first table 4. Table -> Autoformat styles -> Press OK 5. Table -> Autoformat styles -> Select the next style & press OK 6. Repeat 4 (few times) Actual Results: Large memory bumps on every change Expected Results: A bit more efficient behavior Reproducible: Always User Profile Reset: No Additional Info: Version: 6.3.0.0.alpha1+ Build ID: f5b9590fc06811a9dff550c6998d1d1088507e23 CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; Locale: nl-NL (nl_NL); UI-Language: en-US Calc: CL
Created attachment 151675 [details] Example file
I can't confirm that with Version: 6.3.0.0.alpha1+ (x64) Build ID: e92dcfdc7bd7b237e0bee26ff226a102d9e8e766 CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2019-05-14_00:00:57 Locale: en-US (de_DE); UI-Language: en-US Calc: threaded
Created attachment 151826 [details] Screencast Version: 6.3.0.0.alpha1+ Build ID: 63b39fe87644587210214198fb67d6b3fb3343c5 CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2019-05-27_01:42:59 Locale: it-IT (nl_NL); UI-Language: en-US Calc: CL
I'm sorry Telesto, but I mixed up CPU and memory usage. I confirm the bug with Version: 6.3.0.0.alpha1+ (x64) Build ID: e92dcfdc7bd7b237e0bee26ff226a102d9e8e766 CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2019-05-14_00:00:57 Locale: en-US (de_DE); UI-Language: en-US Calc: threaded
(In reply to Dieter Praas from comment #4) > I'm sorry Telesto, but I mixed up CPU and memory usage. > No problem, can happen. I'm already happy someone is (un)confirming my reports :-). I'm probably a bit of a pain in the ass QA/Developers with all my bug reports
(In reply to Telesto from comment #5) > I'm already happy someone is (un)confirming my > reports :-). I'm probably a bit of a pain in the ass QA/Developers with all > my bug reports Could be :-) Sometime I wish we could reduce reporting bugs until we have less than 200 unconfirmed bugs.
Tested with Version: 7.1.3.2 (x64) / LibreOffice Community Build ID: 47f78053abe362b9384784d31a6e56f8511eb1c1 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL Actual result LO becones unresponsive for almost 30 seconds with the first change, but works as expected with further changes. Memory usage still increases (+50MB after each change)
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
Changing Autofoirmat Style works well with Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 69d0be09ad81935f7da4b6f8d036c3562357d068 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (de_DE); UI: en-GB Calc: CL threaded => RESOLVED WORKSFORME Additional information: It takes a long time (> 20 seconds) to open document, but that's not the topic of this report.