Steps: 1) Open Draw 2) Using your mouse wheel and Ctrl zoom and and out repeatedly 3) Notice the huge spike in CPU usage For me, my CPU jumped from 5% to 75% just by zooming in and out on a blank page. Testing the same in Writer it would only go to a max of 25%. Wanted to include a screencast, but the screencast app was eating up a huge amount of CPU for the recording. :D Version: 5.2.0.0.alpha0+ Build ID: 72720ac9b934af6f84111ec694fa46555d10a7bd CPU Threads: 2; OS Version: Linux 4.2; UI Render: default; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2016-02-17_19:06:34 Locale: en-US (en_US.UTF-8)
No spike on Win, have to test on Linux Win 7 Pro 64-bit Version: 5.2.0.0.alpha0+ Build ID: ef02de2698d90fd874bddf3146165cbe85487bc5 CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; TinderBox: Win-x86@39, Branch:master, Time: 2016-02-19_23:40:50 Locale: fi-FI (fi_FI)
So i tried it on my laptop which has both Windows 7 and Mint XFCE 17.2 and the performance wasnt as bad as the CPU would only go up to a max of around 30 to 40 percent. Version: 5.2.0.0.alpha0+ Build ID: 6d5eeb6af585ae525645d844cbbd56e76678a0af CPU Threads: 2; OS Version: Windows 6.1; UI Render: default; TinderBox: Win-x86@39, Branch:master, Time: 2016-02-22_00:12:04 Locale: en-US (en_US) Version: 5.2.0.0.alpha0+ Build ID: 0b1da98da44bc9acb9e42a5cd1842adf9d82a415 CPU Threads: 2; OS Version: Linux 3.13; UI Render: default; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2015-12-22_05:54:37 Locale: en-US (en_US.UTF-8)
Well, if I really scrub the mousewheel back and forth like my life depended on it, I can get it to use 57-58% CPU max.. or hover at 51%. But if I scroll in a more laidback way, it's like 20-30% (still pretty vigorous scrolling). Version: 5.2.0.0.alpha0+ Build ID: 8fab3bf91331a4ac9e3b8f44a46f579dbf7aeafb CPU Threads: 8; OS Version: Linux 4.4; UI Render: default; Locale: fi-FI (fi_FI.UTF-8)
I confirm the very slow zoom and slide. Top shows that 'Xorg' process cpu usage rises up to 99%. Version: 5.2.0.4 Build ID: 066b007f5ebcc236395c7d282ba488bca6720265 CPU Threads: 2; OS Version: Linux 3.16; UI Render: default; Locale: ru-RU (en_GB.UTF-8)
The performance become much better if I turn off Anti-Aliasing: Tools/Options/LibreOffice.org/View setting: Usde anti-aliasing Version: 5.2.0.4 Build ID: 066b007f5ebcc236395c7d282ba488bca6720265 CPU Threads: 2; OS Version: Linux 3.16; UI Render: default; Locale: ru-RU (en_GB.UTF-8)
ZSerg: would you like to join the QA team? Info: https://wiki.documentfoundation.org/QA/ru You can meet us on IRC: https://wiki.documentfoundation.org/QA/IRC
** 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.4.1 or 5.3.6 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-20170901
Dear Yousuf Philips (jay), 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 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: 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
(In reply to Buovjaga from comment #3) > Well, if I really scrub the mousewheel back and forth like my life depended > on it, I can get it to use 57-58% CPU max.. or hover at 51%. > But if I scroll in a more laidback way, it's like 20-30% (still pretty > vigorous scrolling). > > Version: 5.2.0.0.alpha0+ > Build ID: 8fab3bf91331a4ac9e3b8f44a46f579dbf7aeafb > CPU Threads: 8; OS Version: Linux 4.4; UI Render: default; > Locale: fi-FI (fi_FI.UTF-8) Now I get like 32% max with super intense back and forth scrolling (unrealistic) and the anti-aliasing setting makes no difference. I think we should close this.