Description: Deleting a column causes a full calculation of the row height Steps to Reproduce: 1. Open the attached file 2. Delete the - say - the (empty!) column N 3. Wait until the adapt row height calculation is finished Actual Results: Slow Expected Results: Ideally some speed-up (but well like complicated, not the first "adapt row height" is slow bug) Reproducible: Always User Profile Reset: No Additional Info: Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 99a88c9e55872214ce01d89447d18708e47e956b CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL threaded
Created attachment 187252 [details] Sample
I got a stopwatch time of 7 seconds. These sorts of reports are a bit questionable, but let's set to NEW anyway. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 8cd29dac4046e38bcf14784accab94ad1b4ac4d7 CPU threads: 8; OS: Linux 6.3; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded
(In reply to Buovjaga from comment #2) > I got a stopwatch time of 7 seconds. > > These sorts of reports are a bit questionable, but let's set to NEW anyway. > > Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community > Build ID: 8cd29dac4046e38bcf14784accab94ad1b4ac4d7 > CPU threads: 8; OS: Linux 6.3; UI render: default; VCL: kf5 (cairo+xcb) > Locale: fi-FI (fi_FI.UTF-8); UI: en-US > Calc: threaded My less powerful machine 12 seconds. The 8 seconds is more a simple sample.. you can increase the waiting time by adding more rows with multi-line text.
Dear Telesto, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still present Version: 25.8.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 5c7b3f5dc1f14081eed380999dc029a500784d55 CPU threads: 8; OS: macOS 14.7.4; UI render: Skia/Metal; VCL: osx Locale: nl-NL (nl_NL.UTF-8); UI: en-US Calc: threaded