Bug 127688 - Dotted chapter numbering crashes Writer under Linux
Summary: Dotted chapter numbering crashes Writer under Linux
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.3.1.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: haveBacktrace
Depends on:
Blocks: Chapter-Numbering Crash
  Show dependency treegraph
 
Reported: 2019-09-21 18:46 UTC by Wolfgang Glas
Modified: 2020-09-25 21:01 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Document with dotted chapter numbering crashing LibO under Linux (8.84 KB, application/vnd.oasis.opendocument.text)
2019-09-21 18:46 UTC, Wolfgang Glas
Details
gdb trace (13.80 KB, text/x-log)
2019-09-21 18:56 UTC, Julien Nabet
Details
File with plain chapter numbering to demonstrate CPU loop (8.84 KB, application/vnd.oasis.opendocument.text)
2019-09-23 05:48 UTC, Wolfgang Glas
Details
gdb thread dump when entering a loop when switching to '1.,2.,...' (30.91 KB, text/plain)
2019-09-23 07:51 UTC, Wolfgang Glas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Wolfgang Glas 2019-09-21 18:46:33 UTC
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.
Comment 1 Julien Nabet 2019-09-21 18:56:43 UTC
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
Comment 2 Wolfgang Glas 2019-09-21 20:00:21 UTC
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
Comment 3 Wolfgang Glas 2019-09-23 05:48:58 UTC
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.
Comment 4 Wolfgang Glas 2019-09-23 05:50:18 UTC
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
Comment 5 Wolfgang Glas 2019-09-23 07:51:44 UTC
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.
Comment 6 Julien Nabet 2019-09-23 08:39:24 UTC
The last bt you retrieved should help devs to find the pb.
AFAIC, I can't help here -> uncc myself.
Comment 7 Wolfgang Glas 2019-09-23 08:53:37 UTC
Thanks Julien for your efforts so far, hopefully the devs will have a look on my BT.
Regards, Wolfgang
Comment 8 Xisco Faulí 2019-09-23 11:02:57 UTC
Hello Julien, Wolfgang,
Which is the GTK version debian uses ( dpkg -s libgtk-3-0|grep '^Version' ) ?
is it the same as bug 127450 ?
Comment 9 Wolfgang Glas 2019-09-23 12:49:43 UTC
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