Using this document as an example: https://wiki.documentfoundation.org/images/2/2f/WG42-WriterGuideLO.odt Independent Navigator (not in Sidebar, but docked on left): 1. Open Task Manager or Resource Monitor. 2. Open document. 3. Open Navigator. Note: There is an initial spike of 25% while the document is loading. 4. Expand Text frames and Images in Navigator. 5. Place cursor in document. Result: Cpu usage is 15%. Scrolling through the document is slow. 6. Click on something in the Navigator. Result: Cpu usage drops to anywhere from 1% to 3%. 7. New Text Document or switch to a different application. Result: Cpu usage jumps back up to 15%. Navigator in Sidebar: 1. Open Task Manager or Resource Monitor. 2. Open document. 3. Open Navigator. Note: There is an initial spike of 25% while the document is loading. 4. Expand Text frames and Images in Navigator. 5. Place cursor in document. Result: Cpu usage is 15%. Scrolling through the document is slow. 6. Click on something in the Navigator. Result: Cpu usage drops to anywhere from 1% to 3%. 7. New Text Document or switch to a different application. Result: Cpu usage jumps back up to 15%. 8. Hide Sidebar. 9. Place cursor in document. Result: Cpu usage is 15%. Once Text frames and Images have been expanded, collapsing them does not drop the cpu usage when the cursor is in the document. If you collapse these objects then close and reopen the Navigator, then the cpu usage remains low. Hiding the Navigator in the Sidebar is not the same as closing it and still results in constant cpu usage. Version: 4.4.1.2 Build ID: 45e2de17089c24a1fa810c8f975a7171ba4cd432
Hi @Gordo, thanks for reporting. Please have you tried, modifying graphic settings in: Menu/Tools/Options/LibreOffice/Memory
Changing the memory settings has no effect. Still seeing 15%.
Reproduced both on Win & Linux. Windows peaked at ~15%, when I stopped scrolling at Preface, CPU sat at 10-11%. Focus on Navigator dropped it to 0-3%. Linux (virtual machine) 4.4 peaked at ~30% and after stopping sat at ~17%. 3.3 peaked at ~17% and after stopping sat at ~9%. Already in 3.3 focusing on Navigator dropped the CPU load. Win 7 Pro 64-bit, Version: 4.4.2.2 Build ID: c4c7d32d0d49397cad38d62472b0bc8acff48dd6 Locale: fi_FI Ubuntu 14.10 64-bit Version: 4.4.2.2 Build ID: 40m0(Build:2) Locale: en_US LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.0.5 or 5.1.2 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-04-16
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.2.7 or 5.3.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170522
still repro in Version: 6.3.0.0.alpha0+ Build ID: ed707a4806a489467c6d9be7d1b787dab94b5f78 CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win; Locale: ru-RU (ru_RU); UI-Language: en-US Calc: threaded
Julien, can you try make perfgraph here? I'm just not sure if it will be useful here...
Created attachment 156777 [details] perf flamegraph On pc Debian x86-64 with master sources updated today + enable-symbols + gtk3 rendering and brand new profile, I tried the steps from not sidebar part. Opening file, open navigator, expand Frames, Images, click somewhere on the file, launch Calc
Dear Gordo, 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