Created attachment 103752 [details] A kind of screenshot Hi, Selecting multiple rows and/or columns in Calc eats lots of CPU (100% of one logical CPU to be more precise). To reproduce this: - open any project in LibreOffice Calc; - select several rows and/or columns with mouse left button clicks and keyboard Ctrl button pressed; - look at CPU usage; - continue selecting; ... - sadly, no profit. The larger the selection is, the longer the high CPU usage period is. The process thread is "soffice.bin!main+0x153". This has been tested on Windows 7 both x86 and x64 using three different hardware setups. The screenshot is taken on a quad-core x64 system. This is the behavior of all the "fresh" versions since 4.2.0.x so far. Versions 4.1.x are this-bug-free. Thanks in advance, Artem
happens to me too on Arch Linux. If I select multiple cells or, specifically, holding control and clicking on row numbers, CPU spikes on my laptop
Does this happen with an empty spreadsheet? Also is it still occurring on 4.3 series? Marking as NEEDINFO - if it does not exist with empty spreadsheet, please attach a document that you experience it with and then mark it as UNCONFIRMED. Thanks
This happens with an empty spreadsheet too. The bug was originally submitted with the 4.3.0.4 release version and windows (all) in the info. It annoyed me since 4.2.0.4 release but I decided to wait and see how this ends. Nothing changed with 4.3, so reported it. Looked through the list of bugs, found some that seemed similar but not exactly the same. Anyways, maybe these are connected somehow. Captured a video showing how to reproduce. It's available here - http://youtu.be/wYHie6fkSxE
(In reply to comment #4) > Captured a video showing how to reproduce. It's available here - > http://youtu.be/wYHie6fkSxE Thanks for the clear instructions. Under Debian 7 x86_64 using: - v4.1.6.2 Build ID: 40ff705089295be5be0aae9b15123f687c05b0a ... selecting 11 non-contiguous rows and then 4 non-contiguous columns results in ~4.0% CPU (while selecting) before returning to ~0% once I stop. Under Crunchbang 11 x86_64 using: - v4.2.6.3 Build ID: 3fd416d4c6db7d3204c17ce57a1d70f6e531ee21 ... I only manage the 11 non-contiguous rows before ~100% CPU usage, so this appears related to the large Calc changes in v4.2. Under Debian 7 x86_64 using: - v4.3.1.2 Build ID: 958349dc3b25111dbca392fbc281a05559ef6848 ... I am able to select 11 non-contiguous rows and then 2-3 non-contiguous columns before CPU usage reached ~100%. This appears to be a mild improvement over v4.2. Under Crunchbang 11 x86_64 using: - v4.4.0.0.alpha0+ Build ID: 037d03b9facb414ba6be01fa6ee92fc7ca89f70c TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2014-09-11_00:32:52 ... I am able to select 11 non-contiguous rows and then 4 non-contiguous columns before CPU usage reached ~100%. This again appears to be a mild improvement over v4.3. Confirmed. Status set to NEW. Whiteboard set to PossibleRegression.
** 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.1 or preferably 5.0.2.2 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 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: 2015-10-14
Windows 7 x64, LibreOffice 5.0.2.2 (37b43f919e4de5eeaca9b9755ed688758a8251fe), works fine.
Migrating Whiteboard tags to Keywords: (possibleRegression) [NinjaEdit]