Description: Crash after undo they modifications made by track & changes (document comparison) Steps to Reproduce: 1. Download attachment 166847 [details] 2. Open the attached file (export of attachment 166847 [details] to DOCX) 3. Edit -> Track changes -> Compare Document -> Select the ODT 4. Accept all or reject all (maybe 2 different bugs?) 5. CTRL+Z everything -> crash Probably to many undo-steps Actual Results: Crash Expected Results: No crash Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.0.0.alpha0+ (x64) Build ID: 94e6e140491de31c0788c91af855a75a3bb12709 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
No crash in Version: 5.4.0.0.alpha1+ Build ID: 9feb7f7039a3b59974cbf266922177e961a52dd1 CPU threads: 4; OS: Windows 6.29; UI render: GL; Locale: nl-NL (nl_NL); Calc: CL
no attached file
Created attachment 166870 [details] Example file
(In reply to Xisco Faulí from comment #2) > no attached file It's always the same :-(
Created attachment 166955 [details] backtrace from assertion At the end of step 3., my LO crashes with message (rewrapped): soffice.bin: /home/terry/lo_hacking/git/libo6/sw/source/core/bastyp/index.cxx:234: virtual SwIndexReg::~SwIndexReg(): Assertion `!m_pFirst && !m_pLast && "There are still indices registered"' failed. This is in a local build of commit fbd6d6cc (2020-10-30), configured with --enable-debug , built and running on debian-buster. I suspect that my LO is crashing earlier in STR because of --enable-debug. I have found two bugs already reporting the same assertion: - bug 126539, upon reject changes. - bug 130699, upon other undo/redo. Five or six of frames leading up to the assertion in the backtraces attached to those bugs match function names with my backtrace.
No crash for me on Fedora 32, either build id 94e6e140491de31c0788c91af855a75a3bb12709 or today's master.