Description: Crash swlo!sw::WriterMultiListener::StartListening Steps to Reproduce: 1. Open the attached file 2. CTRL+A 3. CTRL+C 4. CTRL+N 5. CTRL+V 6. CTRL+Z 7. CTRL+SHIFT+V -> RTF Actual Results: Crash Expected Results: No crash Reproducible: Always User Profile Reset: No Additional Info: Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 66013201749df7d5ac5ddaf377a7b3732518a93b 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 169348 [details] Example file
Also in Version: 7.0.0.0.beta1+ (x64) Build ID: 2891e91a513520d68ea2b8c59c14335861a15253 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 with Version: 6.4.0.0.beta1+ (x64) Build ID: 20be5cd0bdc57d812bf34a2debfe48caa51de881 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: GL; VCL: win; Locale: nl-NL (nl_NL); UI-Language: en-US Calc: CL
Created attachment 169349 [details] BT without symbols
Created attachment 169364 [details] bt with debug symbols On pc Debian x86-64 with master sources updated today, I could reproduce this.
I tried to bisect it with bibisect-linux64-6.4 but the results are not accurate. @Telesto, please, bisect it on your side
(In reply to Xisco Faulí from comment #5) > I tried to bisect it with bibisect-linux64-6.4 but the results are not > accurate. > @Telesto, please, bisect it on your side So you could reproduce this with 6.4..while i'm looking bibisect 7.0 repro. Attempted a bibisect.. but bogus too
Yeah, it is somehow unreliable. It crashed for me even in the oldest of Linux 6.3 repo. Sometimes you have to attempt it as many as 5 times. As the steps are simple, I recommend recording a macro of them, so you can run them easily without going crazy (if you want to still investigate with older repos).
No crash with macOS Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 8635c9aa8c6f1078a9e220076d5a08daf30077e8 CPU threads: 8; OS: Mac OS X 12.3.1; UI render: Skia/Metal; VCL: osx Locale: nl-NL (nl_NL.UTF-8); UI: en-US Calc: threaded
Crashed on first try both with 7.4.3 and with latest of 7.5 bibisect repo on Linux Version: 7.5.0.1.0+ (X86_64) / LibreOffice Community Build ID: 09848e94d20c067499ad69edf81fa80a45d0a632 CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded
16969a30ad77188fe5452c42d122b205c4274948 is the first bad commit commit 16969a30ad77188fe5452c42d122b205c4274948 Author: Jenkins Build User <tdf@maggie.tdf> Date: Fri Nov 24 09:48:50 2023 +0100 source 9137bd2dd3ab66ffa783fc15a1add1e9cf541460 source 9137bd2dd3ab66ffa783fc15a1add1e9cf541460 Bisected with: linux-64-24.2 Adding Cc: to Frank Steiner
(In reply to Federico Castellani from comment #10) > 16969a30ad77188fe5452c42d122b205c4274948 is the first bad commit > commit 16969a30ad77188fe5452c42d122b205c4274948 > Author: Jenkins Build User <tdf@maggie.tdf> > Date: Fri Nov 24 09:48:50 2023 +0100 > > source 9137bd2dd3ab66ffa783fc15a1add1e9cf541460 > > source 9137bd2dd3ab66ffa783fc15a1add1e9cf541460 > > Bisected with: linux-64-24.2 > > Adding Cc: to Frank Steiner Hmm, that would be a time-traveling Frank, so let's undo the changes. Federico: as a beginner, if you see a report like this, where people are talking about how difficult it is to bisect, better to skip it.
Sorry, I don't understand it :) In which sense is patch 16969a30ad77188fe5452c42d122b205c4274948 "the first bad commit", what does that mean? I've no experience with bibisect. How could the patch be related to the crashes if those are all reported for versions that didn't contain this patch (it was added only on November 24th 2023)...?
(In reply to Frank Steiner from comment #12) > Sorry, I don't understand it :) In which sense is patch > 16969a30ad77188fe5452c42d122b205c4274948 "the first bad commit", what does > that mean? I've no experience with bibisect. > > How could the patch be related to the crashes if those are all reported for > versions that didn't contain this patch (it was added only on November 24th > 2023)...? See my comment 11, the result was a mistake by a beginner practicing bisecting.
Sorry, yes, I got that wrong :-)