Bug 159053 - Crash in: SwContentTree::UpdateTracking()
Summary: Crash in: SwContentTree::UpdateTracking()
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.5.6.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-01-07 00:25 UTC by Toby
Modified: 2024-08-08 03:16 UTC (History)
3 users (show)

See Also:
Crash report or crash signature: ["SwContentTree::UpdateTracking()"]


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Toby 2024-01-07 00:25:13 UTC
This bug was filed from the crash reporting server and is br-9b5e137d-c1ce-4fe4-8902-6b17b88cbee7.
=========================================

In a Writer document, I had lots of URLs as hyperlinks, with the format:
https://www.reddit.com/r/Test/comments/aabbcc/is_this_good

I tried to find "_" and replace with " ". I believe I clicked 'Find next' and it crashed.

Unfortunately I can't recreate the crash.
Comment 1 Xisco Faulí 2024-01-08 10:34:30 UTC
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. 
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
(Please note that the attachment will be public, remove any sensitive information before attaching it. 
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Comment 2 Toby 2024-01-08 14:15:22 UTC
Unfortunately, after recovery, the document did not exhibit the same behaviour again when I re-tried the find & replace.

I've tried adding more of the same sort of URL to the document, but it just doesn't crash now. It was 8 pages, with a dozen URLs and lots of editing, so perhaps it was something to do with that, but I don't understand the crash trace to recreate the conditions, sorry.

I know that being unable to reproduce the bug means it's difficult to trace and unlikely to get fixed, oh well.
Comment 3 Stéphane Guillou (stragu) 2024-01-09 12:58:16 UTC
Seeing that the crash signature started popping up in 7.4, I'm wondering if it's related to Jim's changes around SwContentTree::UpdateTracking() back then.
https://opengrok.libreoffice.org/xref/core/sw/source/uibase/utlui/content.cxx?r=e683cf0a#4147

Can you please test again with your document and the Navigator open?
Comment 4 Stéphane Guillou (stragu) 2024-01-09 13:38:54 UTC
Actually, the signature is not seen since 7.6.3, so I'm wondering if Noel's work for bug 153519 has already fixed it...
Noel, what do you think?
Comment 5 QA Administrators 2024-07-08 03:16:39 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2024-08-08 03:15:59 UTC
Dear Toby,

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