Bug 138677 - LO Writer crashes when length of Table of Contents reaches a Page Break
Summary: LO Writer crashes when length of Table of Contents reaches a Page Break
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.4.7.2 release
Hardware: x86-64 (AMD64) macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-12-05 15:40 UTC by Pfuschi
Modified: 2021-09-09 03:43 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
Final document done with the solution mentioned in the bug report except last page with information to persons. (9.14 MB, application/vnd.oasis.opendocument.text)
2020-12-21 23:45 UTC, Pfuschi
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Pfuschi 2020-12-05 15:40:16 UTC
Description:
Composing document. * From time to time updating or editing ToC. At one time LO will stall on this action (rotating ball). LO needs to be killed. 
When restarting LO and recovering document, this continues adding pages in the hundreds. Need to close document. Upon reopening all looks normal but: continue at *.
"Findings" (after 3 hours of desperation): 
Document has a cover sheet, that is not counted in page numbering. 2nd page is a welcome note and ends with a Page Break. 3rd page is ToC. Content starts on 4th page as a new page, therefore 3rd page (ToC) ends with Page Break.
When length of ToC reaches end of page and a ToC-Action is attempted, LO stalls, see above.
"Solution":
Added enough Line Breaks on ToC page, so a new page was formed. ToC extends now in new page (new 4th).
Conclusion:
ToC process is not capable of extending into a needed new page and lets LO stall/crash.



Steps to Reproduce:
1. see description above
2.
3.

Actual Results:
see description above

Expected Results:
see description above


Reproducible: Always


User Profile Reset: No



Additional Info:
none
Comment 1 Telesto 2020-12-05 16:07:07 UTC
Is it possible to share an example file demonstrating the issue described.. attempting to rebuild same circumstances sounds like quite an exercise
Comment 2 Julien Nabet 2020-12-06 08:43:33 UTC
You can also give a try to 7.0.3. Indeed, even if there's a bug in 6.4.7, there won't be any new official version since it's EOL (see https://wiki.documentfoundation.org/ReleasePlan/6.4).
Comment 3 Pfuschi 2020-12-21 23:45:56 UTC
Created attachment 168391 [details]
Final document done with the solution mentioned in the bug report except last page with information to persons.
Comment 4 Julien Nabet 2020-12-22 22:33:41 UTC
On pc Debian x86-64 with master sources updated today, I don't reproduce a crash.

In the meantime, 7.0.4 has been released.
Comment 5 Xisco Faulí 2021-02-09 13:14:39 UTC
Thank you for reporting the bug.
Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Comment 6 QA Administrators 2021-08-09 03:42:26 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2021-09-09 03:43:05 UTC
Dear Pfuschi,

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