Bug 135116 - Undo accept tracking changes takes +/- 2 minutes to respond
Summary: Undo accept tracking changes takes +/- 2 minutes to respond
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.2.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, perf, regression
Depends on:
Blocks: Track-Changes Undo-Redo
  Show dependency treegraph
 
Reported: 2020-07-24 20:35 UTC by Telesto
Modified: 2025-05-14 03:55 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
Example file (19.12 MB, application/vnd.oasis.opendocument.text)
2020-07-24 20:41 UTC, Telesto
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2020-07-24 20:35:43 UTC
Description:
Undo accept tracking changes takes +/- 2 minutes to respond

Steps to Reproduce:
1. open the attached file
2. Edit -> Manage -> Accept all changes
3. Undo everything (there are additional steps added.. or press CTRL+Z rather often.. or click the undo drop down)

Actual Results:
1 minute 50 seconds in 7.1

Expected Results:
25 seconds


Reproducible: Always


User Profile Reset: No



Additional Info:
Found in
7.1

35 seconds in
6.2 

15 seconds in
6.0
Comment 1 Telesto 2020-07-24 20:41:46 UTC
Created attachment 163493 [details]
Example file
Comment 2 Xisco Faulí 2021-02-09 15:09:08 UTC
Dear Telesto,
Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ?
You can install it alongside the standard version.
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build
Comment 3 Buovjaga 2021-02-22 16:18:30 UTC
The undo action was almost instantaneous

Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 385808a2dff7300ec0120fdd5e8acfad8f86e50d
CPU threads: 2; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win
Locale: fi-FI (fi_FI); UI: en-US
Calc: threaded
Comment 4 Telesto 2021-02-22 18:12:37 UTC
I still reproduce
Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 385808a2dff7300ec0120fdd5e8acfad8f86e50d
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
Comment 5 Ezinne 2021-11-07 15:49:25 UTC
Not reproducible in:

Version: 7.3.0.0.alpha0+ / LibreOffice Community
Build ID: 86d11097cd4a2ae4a6b4e6b35e28a6075376d67a
CPU threads: 8; OS: Linux 5.11; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded


I did not experience any delay in the Undo action. It occurred almost immediately.
Comment 6 raal 2022-02-12 14:01:08 UTC
I can confirm with Version: 7.4.0.0.alpha0+ / LibreOffice Community
Build ID: 1c0aa970650ffc7c749e0b5ea655ebb2d137c8ae
CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: gtk3
Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US
Calc: threaded Jumbo

7.4: 1,5 min
bibisect-linux-64-6.4 oldest: 0,5 min
Comment 7 raal 2022-02-12 14:55:17 UTC
Bisected with linux-64-6.5, the times are 1+ min and 2+ mins.

This seems to have begun at the below commit.
Adding Cc: to Bjoern Michaelsen; Could you possibly take a look at this one?
Thanks
 355ccbed0fb0d6c0881956db790d02170bdcf676 is the first bad commit
commit 355ccbed0fb0d6c0881956db790d02170bdcf676
Author: Jenkins Build User <tdf@pollux.tdf>
Date:   Thu Mar 19 07:52:58 2020 +0100

    source 05eded8a0dd114ba0f24f31762479e178f1419a1

https://git.libreoffice.org/core/+/05eded8a0dd114ba0f24f31762479e178f1419a1
   reffld.cxx: SwIterator no more .
Comment 8 QA Administrators 2025-05-14 03:55:46 UTC
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