Description: CPU usage for selecting text has increased since 5.1 Steps to Reproduce: 1. Open Writer 2. Disable Automatic spell checking (SHIFT+F7)Tools -> Spell Checking 3. Open attachment 134007 [details] 4. Open a CPU monitoring tool 5. Press CTRL+A -> Notice a CPU (25%) spike for around 5 seconds Actual Results: CPU usage is spiking for around 5 seconds with LibO6. Bit less in older versions. Expected Results: Shouldn't happen, as it didn't happen before. Something similar to LibO5.0. Around 7% for 2 seconds Reproducible: Always User Profile Reset: No Additional Info: Found in Version: 6.0.0.0.alpha0+ Build ID: c5a93cad149618bbd43632f1660a558c34bdbf7e CPU threads: 4; OS: Windows 6.3; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-10-07_01:04:25 Locale: nl-NL (nl_NL); Calc: CL and in LibO5.1.0.0 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0
Created attachment 136829 [details] Partial bibisect log I attempted a bibisect, but got stuck because the file keeps running at 100% (at some point).
Confirmed with 5.4 vs. 4.4 on Win 10
I probably reported this multiple times, sorry. Most likely bug 113105 (or bug 113137) Xisco's opinion for bug 113105 -> Taking into account it's a 1486 pages file, I would say it's kind of expected -> NOTABUG The test file posted here is 985 pages.. So not sure what to do.. I would still call it a bug (it did work better in the past) only with a low & minor importance. Closing feels like sweeping it under the carpet..
** 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 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
Cannot reproduce with Version: 7.1.0.0.alpha0+ Build ID: <buildversion> CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3 Locale: de-DE (de_DE.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2020-08-05_04:03:50 Calc: threaded Closing as NOTABUG as this was also mentioned from the bug opener.