Steps to reproduce: 1. Open attachment 54867 [details] from bug 44194 2. Select all 3. Format - Spacing - Line Spacing: 1.5 -> Crash Reproduced in Version: 6.3.0.0.alpha0+ Build ID: 90b13c2c406ec2cdddfa6580edb401c0d07feae6 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded
a first bisection points to https://cgit.freedesktop.org/libreoffice/core/commit/?id=107f0e6dba57a5b27366a35a5cdb184079546df0, however it also crashes before that commit if we play around with the line spacing.
I confirm it with Version: 6.3.0.0.alpha0+ (x64) Build ID: 421e6fc3cd2e6fe37afbef341e2d0ad7b8edde37 CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2019-04-07_01:12:58 Locale: en-US (de_DE); UI-Language: en-US Calc: threaded
Created attachment 150818 [details] gdb bt On pc Debian x86-64 with master sources updated today, I could reproduce this. I also noticed these kinds of logs during opening: warn:legacy.osl:29454:29454:sw/source/filter/ww8/ww8par2.cxx:485: What! ... warn:legacy.osl:29454:29454:sw/source/filter/ww8/ww8par2.cxx:485: What! warn:legacy.osl:29454:29454:sw/source/filter/ww8/ww8par2.cxx:3535: Panic, stop table with no table!
Created attachment 150824 [details] gdb session with backtraces from throws and catches I have reached a result very similar to Julien's in comment 3, collecting backtraces from throw's and catch's along the way. Some line numbers: line what ---- -------------------------------------------------------- 187 ready to adjust spacing; set catchpoints 203 exception thrown 267 exception caught 328 exception thrown 393 exception caught 455 exception thrown 521 exception caught 584 exception thrown 647 exception caught 707 exception thrown 791 exception caught 875 exception thrown 906 exception caught 941 SIGSEGV At the SIGSEGV, Julien and my backtraces show different functions in frame #0; after that they show the same function names. My observations are from a local build of commit 3a5d7836 (2019-04-09), configured: CC=ccache /usr/bin/gcc CXX=ccache /usr/bin/g++ CCFLAGS=-Wshadow --with-jdk-home=/usr/lib/jvm/default-java --enable-split-debug --enable-gdb-index --enable-ld=gold --enable-option-checking=fatal #--enable-dbgutil --enable-debug --without-system-postgresql --without-myspell-dicts --with-extra-buildid --without-doxygen --with-external-tar=/home/terry/lo_hacking/git/src --without-package-format built and running on debian-buster. I am removing keyword wantBacktrace and adding haveBacktrace.
No crash Version: 7.0.0.0.alpha0+ (x64) Build ID: 4475bcd83aac7e033fc5250f268eb922bd471e7b CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win; Locale: nl-NL (nl_NL); UI-Language: en-US Calc: CL
FWIW: 1. Open attachment 54867 [details] from bug 44194 2. Select all 3. CTRL+N 4. Special Paste RTF -> Crash (no crash with 6.4.3.2; but probably some timing aspect) Version: 7.0.0.0.alpha0+ (x64) Build ID: f924658e45f256544e43c3fdb2af9b585d0f0933 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win; Locale: nl-NL (nl_NL); UI-Language: en-US Calc: CL
Still crashing in Version: 7.0.0.0.alpha1+ Build ID: 8209c2569f5726f9ed29f75d30efdccb94f98fe5 CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI: en-US Calc: with 1. Open attachment 54867 [details] from bug 44194 2. Select all 3. Format - Spacing - Line Spacing: 1.5 4. Undo
*** Bug 132384 has been marked as a duplicate of this bug. ***
Seems fixed in GTK3. Repro 6.4 steps from c0, 7.0 crash already on Format, no repro 7.2 and 7.4+. I couldn't repro in Windows. So verification would be prudent.
7.1 master crash, 7.2 oldest not (just blinking) so not reverse b. for me. Maybe it's about profile or about the moment when Undo is pressed.