This bug was filed from the crash reporting server and is br-205cd92e-417d-4dbc-808d-1da1ef0579b6. ========================================= Saving a file Version: 5.4.3.2 (x64) Build ID: 92a7159f7e4af62137622921e809f8546db437e5 CPU threads: 4; OS: Windows 6.19; UI render: default; Locale: es-ES (es_ES); Calc: group OpenGL.log DriverVersion: 21.20.16.4550 DriverDate: 11-11-2016 DeviceID: PCI\VEN_8086&DEV_5916&SUBSYS_380117AA&REV_02 AdapterVendorID: 0x8086 AdapterDeviceID: 0x5916 AdapterSubsysID: 0x380117aa DeviceKey: System\CurrentControlSet\Control\Video\{8CD6695F-B514-11E7-B258-B5AD865BD680}\0001 DeviceString: Intel(R) HD Graphics 620
Do you know the steps to reproduce this issue?
No I think it was saving a writer file with password. But it didn't happen again.
I'm not a developer, but I assume, that it is almost impossible to reproduce this bug without further informations. So I propose to close this bug and to reopen it, if it happens again and you can give some more informations. Do you agree?
https://crashreport.libreoffice.org/stats/signature/SfxSlotPool::GetSlotPool%28SfxViewFrame%20*%29 4204 similar reports! For me it's like confirmation.
(In reply to m.a.riosv from comment #2) > No I think it was saving a writer file with password. But it didn't happen > again. Do you think there was something in the clipboard when you tried to save the document ?
Who knows?
Any relation with bug 100270 ?
It's 10650 reports now, latest for LO 6.0. Xisco, in my view, cases like this should be discussed at ESC, maybe as "Most Pressing Bugs". And to have it in written: rules for keeping this open and confirmed, is a number of reports enough and can this ever be resolved like this, only with reports.
(In reply to Timur from comment #8) > It's 10650 reports now, latest for LO 6.0. > Xisco, in my view, cases like this should be discussed at ESC, maybe as > "Most Pressing Bugs". > And to have it in written: rules for keeping this open and confirmed, is a > number of reports enough and can this ever be resolved like this, only with > reports. It has been already mentioned in ESC meeting in the crash reporter section.
Created attachment 139127 [details] some rough notes / code-reading. Not sure that bug is a duplicate no; but I spent a little while chasing this one down. It -looks- from ptr arithmetic from the 0x14 crash-site, as if (somehow) we have a NULL SfxApplication - rather odd. Need to chase further. The crash happens during shutdown.
Something of a hack here: https://gerrit.libreoffice.org/48007 may help - hard to say since we can't reproduce this easily. Possibly it only shows on very busy machines where the user events are not processed fully before save (or something) =)
Created attachment 139132 [details] more notes ... Actually - having a large number of writer windows open - perhaps with some floating windows too and then exiting -might- be enough to trigger this - if someone wants to play =)
Michael Meeks committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=ad7e6339e5e5cf465a2ef25442099eb59f1a0deb tdf#113755 - avoid null ptr de-reference during shutdown. It will be available in 6.1.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
From https://wiki.documentfoundation.org/Releases/5.3.6/RC1 looks like Caolan had some patches for null deref.
Michael, do you think it's safe to backport to 6.0 so we can track reports if they reoccur? And please comment on my previous message, what are "ofz".
I back-ported to 6-0 but no 2nd review (yet): https://gerrit.libreoffice.org/48013 > looks like Caolan had some patches for null deref. It is a favourite programmers hobby de-referencing null =) > And please comment on my previous message, what are "ofz". OFZ ? =)
(In reply to Timur from comment #15) > Michael, do you think it's safe to backport to 6.0 so we can track reports > if they reoccur? > And please comment on my previous message, what are "ofz". Hi Timur, The backport to 6-0 is waiting for review in https://gerrit.libreoffice.org/#/c/48013/ and I've just cherry-picked it to 6-0-0 as well -> https://gerrit.libreoffice.org/#/c/48179/. 'ofz' stands for oss-fuzz: https://github.com/google/oss-fuzz
Michael Meeks committed a patch related to this issue. It has been pushed to "libreoffice-6-0": http://cgit.freedesktop.org/libreoffice/core/commit/?id=a747dfef9c723808e12e802a2cc2f5688ab255fa&h=libreoffice-6-0 tdf#113755 - avoid null ptr de-reference during shutdown. It will be available in 6.0.1. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Michael Meeks committed a patch related to this issue. It has been pushed to "libreoffice-6-0-0": http://cgit.freedesktop.org/libreoffice/core/commit/?id=877d94e5e90bf6599a30aa33e8504e4bcd332654&h=libreoffice-6-0-0 tdf#113755 - avoid null ptr de-reference during shutdown. It will be available in 6.0.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
It seems the crash is no longer reported in http://crashreport.libreoffice.org/stats/version/6.0.0.3. @Michael Meeks, i guess we can close it as RESOLVED FIXED now. backported to 5-4 branch -> https://gerrit.libreoffice.org/#/c/49103/
Michael Meeks committed a patch related to this issue. It has been pushed to "libreoffice-5-4": http://cgit.freedesktop.org/libreoffice/core/commit/?id=615f4846751fb669ea28cc092eadfd3842ab3220&h=libreoffice-5-4 tdf#113755 - avoid null ptr de-reference during shutdown. It will be available in 5.4.6. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
A polite ping to Michael Meeks: Could you please close it as RESOLVED FIXED ? Thanks
(In reply to Xisco Faulí from comment #20) > It seems the crash is no longer reported in > http://crashreport.libreoffice.org/stats/version/6.0.0.3. Bug summary lists 4 reports for 6.0.0.3 and 2 for 6.0.1.1.
There are still reports for Version: 5.4.7.2 and Version: 6.0.4.2. So far no 6.1.
Dear m.a.riosv, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Seems like fixes decreased crashes considerably, from dozens of thousands in 5.4 to dozens. 48 crashes for latest Version: 7.0.3.1, cannot filter but seems like it's for Build Architecture is x86, Windows 10. Not sure anyone will look into this anymore.
(In reply to Timur from comment #26) > Seems like fixes decreased crashes considerably, from dozens of thousands in > 5.4 to dozens. > 48 crashes for latest Version: 7.0.3.1 [...] Looks like there hasn't been a crash of this type since: - 7.2.7.2. This issue can probably be closed now. - - - - PS. As of today, there are still crashes using !!!5.4.0.3 (released in November 2017)!!! Ugh, ancient, ancient versions still floating around out there...