Description: Undo deleting a large table slow. See also bug 136748 Steps to Reproduce: 1. open the attached file (see also bug 136748; same file) Actual Results: 40 seconds Expected Results: 15-20 seconds Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.0.0.alpha0+ (x64) Build ID: ed4f610f4a3de12016f8308a17b6ad4f86e9d67a 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
Created attachment 165491 [details] Example file
Pretty decent with Versie: 4.4.7.2 Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600 Locale: nl_NL -> 15 seconds
16 seconds with 6.0
30 seconds in Version: 7.1.0.0.alpha0+ Build ID: 3a22f5a589e822e7ca8bbb00e38a3aff93ed7ba5 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-US (ro_RO.UTF-8); UI: en-US Calc: threaded
Confirmed with Version: 7.1.0.0.alpha0+ Build ID: 3a22f5a589e822e7ca8bbb00e38a3aff93ed7ba5 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-US (ro_RO.UTF-8); UI: en-US Calc: threaded
Can you re-test? It is rather instant for me Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 58a5bd793a2ed57077fc598281cc74e16373b877 CPU threads: 8; OS: Linux 5.13; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded
My system is freezing for 30 seconds. After that I have a window with "LibreOfficeDev 7.3 Document Recovery. Due to an error LibreOfficeDev crashed."
Created attachment 174612 [details] my CPU 100% 4 cores you can see in the image 1 of the 4 cores is at 100% and after I click don't recover is going down again.
Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: fbe183bbb05220a4ccc51952445b1797bb498403 CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded
Created attachment 174613 [details] Perf flamegraph Hmm, it was not so instant for me after all - even though the table reappears, the UI is blocked for some 5 secs. Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 567c6c123094bf58c14ddac94e962cc62bc839b3 CPU threads: 8; OS: Linux 5.13; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded
Noel Grandin committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/af8cb1039fd0cce86d771f4765c7d73c9f39b5a7 tdf#136749 std::map -> unordered_map It will be available in 7.6.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Noel Grandin committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/59036776b92c0f4ad2edd1bafd332f7a4ee87cdc tdf#136749 no need to use maMutex in SwAccessibleMap It will be available in 7.6.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
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
12 sec Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 798b43c4ef433d9f2cbfa431ebdf9ec35c3b8a39 CPU threads: 16; OS: Windows 11 X86_64 (10.0 build 26100); UI render: Skia/Vulkan; VCL: win Locale: de-DE (de_DE); UI: en-US Calc: threaded over 60 sec Version: 25.2.2.2 (X86_64) / LibreOffice Community Build ID: 7370d4be9e3cf6031a51beef54ff3bda878e3fac CPU threads: 16; OS: Windows 11 X86_64 (10.0 build 26100); UI render: Skia/Vulkan; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: threaded
bisected with win64-25.2 commit 1021f3e47ab2827d1b7872f641a21b84efcc2c91 Author: Norbert Thiebaud <nthiebaud@gmail.com> Date: Sat Oct 19 00:10:17 2024 -0700 source bfbaeb8192447265bdd78d1be4990947d135eb6e source bfbaeb8192447265bdd78d1be4990947d135eb6e instdir/program/setup.ini | 2 +- instdir/program/vcllo.dll | Bin 13686784 -> 13686272 bytes instdir/program/vclplug_winlo.dll | Bin 2587648 -> 2587648 bytes instdir/program/version.ini | 2 +- 4 files changed, 2 insertions(+), 2 deletions(-) Results under 20 sec is good, more than 20sec bad. Adding Cc: to <nthiebaud@gmail.com>
(In reply to Jessica from comment #15) > bisected with win64-25.2 > > commit 1021f3e47ab2827d1b7872f641a21b84efcc2c91 > Author: Norbert Thiebaud <nthiebaud@gmail.com> > Date: Sat Oct 19 00:10:17 2024 -0700 > > source bfbaeb8192447265bdd78d1be4990947d135eb6e > > source bfbaeb8192447265bdd78d1be4990947d135eb6e > > instdir/program/setup.ini | 2 +- > instdir/program/vcllo.dll | Bin 13686784 -> 13686272 bytes > instdir/program/vclplug_winlo.dll | Bin 2587648 -> 2587648 bytes > instdir/program/version.ini | 2 +- > 4 files changed, 2 insertions(+), 2 deletions(-) > > Results under 20 sec is good, more than 20sec bad. > > Adding Cc: to <nthiebaud@gmail.com> The name you see in "Author" in the binary commits is the name under which the binaries were built. Actually in this case, I believe the name is a historical remnant as Xisco does the builds now. Please see the paragraph starting with "After the final step in the bibisecting process, you are presented with the first bad commit" in https://wiki.documentfoundation.org/QA/Bibisect#General_Instructions This report is from 2020, referencing 7.1 as the earliest known bad version. Thus, your finding concerning a 2024 regression would be more appropriate as a new report.
The bibisect above was moved to bug 166479 and it might be a feature, not a bug.