Description: Crash/ Freeze after undo changes in an old swx Steps to Reproduce: Steps to Reproduce: 1. Open https://bz.apache.org/ooo/attachment.cgi?id=15387 https://bz.apache.org/ooo/show_bug.cgi?id=24533 2. CTRL+A 3. CTRL+X 4. CTRL+A 5. CTRL+X 6. CTRL+Z 7. CTRL+Z -> 7.1 Freeze 6.4 Crash Actual Results: Freeze or crash Expected Results: Should ideally work Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.0.0.alpha0+ (x64) Build ID: a35c18aeff3b1d8f270db7e094850fb8ba1ab84a CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: GL; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL
Fine with Versie: 4.4.7.2 Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600 Locale: nl_NL
Created attachment 162045 [details] bt with debug symbols (gen) On pc Debian x86-64 with master sources updated today, I got an assertion after just: - Ctrl A - Ctrl X
LibreOffice crashes for me on step 3 after cutting the content Version: 7.1.0.0.alpha0+ Build ID: 11d21b3c1f7754b5d13ae9ea88da562ec74366ff CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Version: 6.3.0.0.alpha1+ Build ID: c98b1f1cd43b3e109bcaf6324ef2d1f449b34099 CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded @Telesto, does it happen for you if you wait a bit after step 3 ?
Buovjaga: I agree with the fact undo/layout is not stable but "critical" for an old format like "swx" + process to reproduce this more "treasure map game" than straightforward ?
(In reply to Julien Nabet from comment #4) > Buovjaga: I agree with the fact undo/layout is not stable but "critical" for > an old format like "swx" + process to reproduce this more "treasure map > game" than straightforward ? Critical tells us about the severity of the effect. The aspect you are thinking of is priority, which I did not touch.
This issue has been fixed by https://cgit.freedesktop.org/libreoffice/core/commit/?id=14e87a4b15d31a34e6053f6194688f3aa23af991. Closing as a dupe of bug 133967 *** This bug has been marked as a duplicate of bug 133967 ***