Steps to reproduce: 1. Open LibreOffice Spreadsheet. 2. Select all cells. 3. Change the font name to anything not installed (ex.: Tahoma). 4. Try navigante cells with cursor keys. Current behavior: High CPU / slowness navigating a empty spreadsheet. Expected behavior: Instantaneous response. Operating System: Linux macrossv 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Enviroment: Gnome Flashback (Metacity) This bug is driving me crazy. This is a fresh instalation, and opening documents from Windows machine now forces to reformat the entire spreadsheet to operate then...
Did you try to use the replacement table (menu Tools > Options > LibreOffice > Fonts) ? Set status to NEEDINFO. Please set it back to UNCONFIRMED once you have provided requested informations. Thank you for your understanding. Best regards. JBF
Yes. I got 100% CPU/slow response even with the replacament table. Creating entries on replacement table deepens a little the problem...
I only get it to about 60% CPU when cursoring up and down furiously, with or without non-installed font. Ubuntu 14.10 64-bit Version: 4.4.0.0.alpha2+ Build ID: 5bff4b016c4b44f4123e0e6a4fd4c0c4dc0cfa2d TinderBox: Linux-rpm_deb-x86_64@46-TDF-dbg, Branch:master, Time: 2014-11-13_00:14:29
I'm getting the slowness with installed fonts too. Steps to reproduce: 1. Open LibreOffice Spreadsheet. 2. Press and hold down key. 3. Select all cells (CTRL+A) 4. Change the font name 5. CRTL+Home and then press and hold down key. (2) never go above ~16% CPU and is very responsive. (5) goes to 100% in one CPU and get sluggish/delayed.
Ah, you are right, I actually forgot to Ctrl-A in my previous test! I changed only some dozens of cells. Now I got to 95% CPU. Let's set as NEW and see what devs think.
** 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.4 or later) 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 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: 2015-12-20
The bug still present at version 5.0.4.2. Tested for Windows 64 bits.
** 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
The bug is still present on lastest of https://www.libreoffice.org/download/ . Version: 5.4.3.2 Build ID: 92a7159f7e4af62137622921e809f8546db437e5 CPU threads: 8; OS: Linux 3.13; UI render: default; VCL: gtk2; Locale: pt-BR (pt_BR.UTF-8); Calc: CL
no repro in Version: 6.5.0.0.alpha0+ (x64) Build ID: 2d736e1a0a2bbd41fe7793d52bbcc7bfc89c7da3 CPU threads: 4; OS: Windows 10.0 Build 18362; UI render: default; VCL: win; Locale: ru-RU (ru_RU); UI-Language: en-US Calc: threaded but it's possibly only Linux bug Buovjaga, can you retest it yourself on Linux machine?
The CPU use is only 10 percentage points higher after changing the font. Let's close. Arch Linux 64-bit Version: 6.5.0.0.alpha0+ Build ID: 94c1f5cfb96a826220b64608cf0ada76d3bdde31 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: kf5; Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US Calc: threaded Built on 14 January 2020