Bug 122692 - Crash in: SvTreeList::Remove(SvTreeListEntry const *)
Summary: Crash in: SvTreeList::Remove(SvTreeListEntry const *)
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.0.7.3 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-13 16:51 UTC by lindsaybigelow@cad2data.com
Modified: 2019-01-22 12:25 UTC (History)
2 users (show)

See Also:
Crash report or crash signature: ["SvTreeList::Remove(SvTreeListEntry const *)"]


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description lindsaybigelow@cad2data.com 2019-01-13 16:51:33 UTC
This bug was filed from the crash reporting server and is br-3ba822a0-f740-4ac0-a033-6eb20164dfd4.
=========================================
Getting this crash several times per day. 
Always occurs on text input key-down. 
Most commonly after a pause of a minute or more. 
Note, document is > 4MB. 

Note, if saving AutoRecovery data @ 10 min intervals is turned OFF, crashes do not seem to occur! (ran AutoRecovery OFF for a few days, no crashes; turned AutoRecovery back ON yesterday, crash occurs today...)
Comment 1 Xisco Faulí 2019-01-13 18:00:33 UTC
Thank you for reporting the bug. To be certain the reported issue is not
related to corruption in the user profile, could you please reset your
Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and
re-test?

I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the issue is still present
Comment 2 lindsaybigelow@cad2data.com 2019-01-14 00:51:00 UTC
(In reply to Xisco Faulí from comment #1)
> Thank you for reporting the bug. To be certain the reported issue is not
> related to corruption in the user profile, could you please reset your
> Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and
> re-test?
> 
> I have set the bug's status to 'NEEDINFO'. Please change it back to
> 'UNCONFIRMED' if the issue is still present

Have restarted in Safe mode. Will come back in a few days with a report. Cheers!
Comment 3 Xisco Faulí 2019-01-17 11:19:45 UTC
(In reply to lindsaybigelow@cad2data.com from comment #2)
> (In reply to Xisco Faulí from comment #1)
> > Thank you for reporting the bug. To be certain the reported issue is not
> > related to corruption in the user profile, could you please reset your
> > Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and
> > re-test?
> > 
> > I have set the bug's status to 'NEEDINFO'. Please change it back to
> > 'UNCONFIRMED' if the issue is still present
> 
> Have restarted in Safe mode. Will come back in a few days with a report.
> Cheers!

Any update ?
Comment 4 lindsaybigelow@cad2data.com 2019-01-20 11:39:06 UTC
No crashes at all since resetting the profile! 
Now I know to try that first! Thank you!
Comment 5 Dieter 2019-01-20 12:57:53 UTC
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. Change to RESOLVED WORKSFORME, if the problem went away.
Comment 6 lindsaybigelow@cad2data.com 2019-01-21 23:47:00 UTC
That would be difficult, as I cannot reproduce the crash at all since resetting my profile! But I will certainly get the latest version, and try to break it! (lol) (Made a donation today BTW)
Comment 7 Xisco Faulí 2019-01-22 12:25:21 UTC
(In reply to lindsaybigelow@cad2data.com from comment #6)
> That would be difficult, as I cannot reproduce the crash at all since
> resetting my profile! But I will certainly get the latest version, and try
> to break it! (lol) (Made a donation today BTW)

Hello,
Thank you very much for the donation.
Let's set this issue as RESOLVED WORKSFORME for the time being. Please, set i back to UNCONFIRMED if you manage to the reproduce the problem again