Bug 164451 - Inserting a table of contents (text document) always crashes Libreoffice
Summary: Inserting a table of contents (text document) always crashes Libreoffice
Status: RESOLVED DUPLICATE of bug 163325
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
24.8.3.2 release
Hardware: All Windows (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisectRequest, regression
Depends on:
Blocks: TableofContents-Indexes Crash
  Show dependency treegraph
 
Reported: 2024-12-24 15:49 UTC by Ian Jarvis
Modified: 2024-12-25 10:52 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Creating ToC without crash (492.36 KB, video/mp4)
2024-12-25 10:11 UTC, Andreas Heinisch
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ian Jarvis 2024-12-24 15:49:35 UTC
Description:
Since the new version and I think the one before, every single time I insert (or don't!) a table of contents (ToC), the system crashes taking down every open libroffice document.
I use ToC in most of my documents and have used it without a problem for many years so it is a major issue for me.
I have sent a crash report, as offered, many times.

Steps to Reproduce:
1.Put in a few headings (eg ctrl+1)
2 Go to the top of the document
3 Select Insert - Table of Contents
4   it crashes
5 There is an opportunity to send a crash report (which I have done many times) and recover the crashed documents which works.


Actual Results:
I carry on without a ToC.

Expected Results:
ToC should insert with all headings listed.


Reproducible: Always


User Profile Reset: No

Additional Info:
[Information automatically included from LibreOffice]
Locale: en-GB
Module: TextDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: no

Version: 24.8.3.2 (X86_64) / LibreOffice Community
Build ID: 48a6bac9e7e268aeb4c3483fcf825c94556d9f92
CPU threads: 8; OS: Windows 10 X86_64 (10.0 build 19045); UI render: Skia/Raster; VCL: win
Locale: en-GB (en_GB); UI: en-GB
Calc: CL threaded
Comment 1 Mike Kaganski 2024-12-25 07:20:50 UTC
The critical for reproduction is that the preview in the ToC dialog is enabled.

Reproducible with Version: 24.8.4.2 (X86_64) / LibreOffice Community
Build ID: bb3cfa12c7b1bf994ecc5649a80400d06cd71002
CPU threads: 24; OS: Windows 11 X86_64 (10.0 build 26100); UI render: default; VCL: win
Locale: de-DE (ru_RU); UI: en-US
Calc: CL threaded

https://crashreport.libreoffice.org/stats/crash_details/1c32bc6e-6955-4b73-afe2-7501831f6342
Comment 2 Mike Kaganski 2024-12-25 07:31:23 UTC
Likely a dupe of bug 163325 - but the sad thing is, that I still reproduce using 24.8.4, which is expected to have the fix.
Comment 3 BogdanB 2024-12-25 09:51:42 UTC
No crash with ToC preview enabled.

Version: 24.8.4.2 (X86_64) / LibreOffice Community
Build ID: bb3cfa12c7b1bf994ecc5649a80400d06cd71002
CPU threads: 16; OS: Linux 6.8; UI render: default; VCL: gtk3
Locale: ro-RO (ro_RO.UTF-8); UI: en-US
Calc: threaded
Comment 4 BogdanB 2024-12-25 09:54:12 UTC
Like is marked in this bug, seems just a Windows specific bug.
Comment 5 Andreas Heinisch 2024-12-25 10:11:38 UTC
Created attachment 198259 [details]
Creating ToC without crash

I could not reproduce the issue using:

Version: 25.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: bc8a86743d122a7df8fcabf59959705895e631f9
CPU threads: 16; OS: Windows 11 X86_64 (build 22631); UI render: Skia/Vulkan; VCL: win
Locale: de-DE (de_DE); UI: en-US
Calc: CL threaded
Comment 6 Mike Kaganski 2024-12-25 10:52:38 UTC
(In reply to Andreas Heinisch from comment #5)

I also can't repro, neither using master, nor Version: 25.2.0.1 (X86_64) / LibreOffice Community
Build ID: ddb2a7ea3a8857aae619555f1a8743e430e146c9
CPU threads: 24; OS: Windows 11 X86_64 (10.0 build 26100); UI render: Skia/Vulkan; VCL: win
Locale: de-DE (ru_RU); UI: en-US
Calc: CL threaded.

Also, before upgrading to 25.2.0.1, I tested using 24.8.4.2 in safe mode, and couldn't repro there, too. So maybe something with the profile, after all...

Let's mark as the duplicate, and reopen later, if turns out that it's really reproducible with clean profile in versions having the fix.

*** This bug has been marked as a duplicate of bug 163325 ***