Created attachment 154348 [details] Document with dotted chapter numbering crashing LibO under Linux The attached docuemnt has been creates using LibO 6.3.1 under MacOS and uses '1., 2., ...' for numbering of chapters. When opening the attached document with LibreOffice-6.3.1 or LIbreOffice-6.1.5 under debian Linux buster, Writer crashes immediately. When switching chapter numbering to '1,2,...' (without dots), the crash disappears.
Created attachment 154349 [details] gdb trace On pc Debian x86-64 with master sources updated today, I don't reproduce this. But I can reproduce this with LO Debian testing package 6.3.2 rc1. I attached gdb trace
Hello Julien, Tank you for looking at this problem, I've no clue, how the debian packaging of LibO might affect this issue. Moreover, in the stack traces there's nothing which point to the actual loading of the odt document :-/ Best Regards, Wolfgang
Created attachment 154376 [details] File with plain chapter numbering to demonstrate CPU loop When changing the chapter numbering in the attached document from '1.,2.,...' to '1,2,...', LibO under debian Linux goes into a 100% CPU loop and the soffice.bin process can only be killed with 'kill -9'. Maybe this effect is easier to trace then the initially reported crash.
My previous comment was wrong, you have to change chapter numbering from '1,2,...' to '1.,2.,...' in order to provoke the CPU loop. Sorry for any inconvenience, Wolfgang
Created attachment 154380 [details] gdb thread dump when entering a loop when switching to '1.,2.,...' This is an attached gdb session backtracing the CPU loop when switching to '1.,2.,...' for chapter numbering.
The last bt you retrieved should help devs to find the pb. AFAIC, I can't help here -> uncc myself.
Thanks Julien for your efforts so far, hopefully the devs will have a look on my BT. Regards, Wolfgang
Hello Julien, Wolfgang, Which is the GTK version debian uses ( dpkg -s libgtk-3-0|grep '^Version' ) ? is it the same as bug 127450 ?
Hello Xisco, These are my versions: $ dpkg -s libgtk-3-0|grep '^Version' Version: 3.24.5-1 wglas@buster-dev:~/tmp$ dpkg -s libreoffice|grep '^Version' Version: 1:6.3.1-1~bpo10+1 Regards, Wolfgang
This bug is unclear status, not generally reproducible. When Julien confirmed, I guess he should not have, if later master (which version?) didn't have crash. Wolfgang, please do: 1. test with user profile reset /deleted 2.test with current LO, like 7.1.
Dear Wolfgang Glas, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Wolfgang Glas, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp