Writer's highlighting tool triggers high CPU use in both Linux Mint 18.2 and Windows 10 in my dual boot. This causes the fan to run and the battery to drain. As soon as I hit the Escape, the CPU drops to zero. The computer has an i5-7200U CPU with Intel 620 graphics. Using the highlighting tool on an old Pentium M laptop creates no such problems with vastly less processing power. I updated the version of LibreOffice that comes with Mint 18.2 to Version: 5.3.6.1, but that didn't help. The Windows version is the safe version from a few days ago.
Thanks for reporting. Sounds like bug 100009
I used this version to reproduce the issue: Version: 5.4.1.2 (x64) Build ID: ea7cb86e6eeb2bf3a5af73a8f7777ac570321527 CPU threads: 4; OS: Windows 6.29; UI render: default; Locale: en-US (en_US); Calc: group I am using Windows 8.1 64bit with i3/ 1.8 GHz and had the same issue also. Once I start the highlighting tool the CPU jump from 2% to more than 25%.
I checked for the problem on five machines running LM 17.1, 17.2 and 17.3 with pentium 4's and one pentium m. The Libre Office versions were 4.2.8.2, 4.4.3.2, and 5.0.3.2. On none of those installs was there a problem. However on a LM 18.2 install on a core duo laptop, with Libre Office 5.1.6.2, highlighting tool used 50% of the cpu, ended by pressing esc. These were all 32 bit Linux Mint installs. On my Acer i5 LM 18.2 the highlighting tool drains the battery in about 1/4 the normal time. I see this bug report described in "Bug 100009 - Using highlight tool makes LibreOffice use 100% of one core" over a year ago and it doesn't seem to be getting fixed. Is there an older version that can be installed on a new 64 bit computer that doesn't have the problem. If not, I'm going to return this computer because the bug interferes what I do most on it. That's disappointing.
I think I might have mistaken what I thought was a 32 bit computer is actually a 64 bit machine. It has a Core Duo t7500 processor but I have a 32 bit Linux Mint 18.2 installed on it. I don't know if that's useful for solving the bug, but I didn't want to make it more difficult. Sorry.
** 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
I updated to Version: 6.1.2.1 and the problem is gone. Thanks for fixing this cpu/highlighting problem. I am again using that extremely useful tool in a great sofware program. -Thanks