X
Thinta lapha ukuze uye kuveshini yamakhalekhukhwini kusayithi.

Isithangami Sabeseki

On Exit, Firefox crashes after writing sessionstore.jsonlz4

Kuphostiwe

The more important problem is this - When I Exit Firefox, Firefox almost always crashes AFTER it has written the sessionstore.jsonlz4 recovery file. I am not sure why Firefox is crashing. Here are my latest crash reports; I just submitted a few that about:crashes told me that I had (for some unknown reason) not yet submitted:

bp-443cad89-7ff9-4b46-a08a-1dc7f0190520	5/20/2019 9:53 AM
bp-206d878c-2234-439f-a4e4-680d50190520	5/20/2019 9:15 AM
bp-470cb28b-9389-4e85-bf84-643240190520	5/20/2019 9:53 AM
bp-5be78b3c-edf3-4aec-bf15-8920c0190517	5/17/2019 4:24 PM
bp-d0f1ce9d-ac2a-40c8-bb87-b58fb0190517	5/17/2019 4:24 PM
bp-cf37500d-4501-4e39-8588-2e0760190516	5/16/2019 10:40 AM
bp-cd595694-e613-4d05-8e0f-713960190515	5/15/2019 8:15 AM
bp-b4e32309-4c8b-4d4e-954b-c6d1b0190513	5/13/2019 9:21 AM

When I look at a crash dump summary, I do not see the crash time. I do see the install time and the install age, but I do not have time to "add" the two to produce the crash time so that I can equate a given crash with my manual log to determine which of these crashed occurred after an Exit. I suggest that the crash dump summary be enhanced to give this information.l And the summary I save (via cut-and-paste) before I submit each crash report does not give the crash dump ID.

For the record, I am running 66.0.5 32-bit on Windows 7, always in safe mode.

The more important problem is this - When I Exit Firefox, Firefox almost always crashes AFTER it has written the sessionstore.jsonlz4 recovery file. I am not sure why Firefox is crashing. Here are my latest crash reports; I just submitted a few that about:crashes told me that I had (for some unknown reason) not yet submitted: <pre><nowiki>bp-443cad89-7ff9-4b46-a08a-1dc7f0190520 5/20/2019 9:53 AM bp-206d878c-2234-439f-a4e4-680d50190520 5/20/2019 9:15 AM bp-470cb28b-9389-4e85-bf84-643240190520 5/20/2019 9:53 AM bp-5be78b3c-edf3-4aec-bf15-8920c0190517 5/17/2019 4:24 PM bp-d0f1ce9d-ac2a-40c8-bb87-b58fb0190517 5/17/2019 4:24 PM bp-cf37500d-4501-4e39-8588-2e0760190516 5/16/2019 10:40 AM bp-cd595694-e613-4d05-8e0f-713960190515 5/15/2019 8:15 AM bp-b4e32309-4c8b-4d4e-954b-c6d1b0190513 5/13/2019 9:21 AM </nowiki></pre> When I look at a crash dump summary, I do not see the crash time. I do see the install time and the install age, but I do not have time to "add" the two to produce the crash time so that I can equate a given crash with my manual log to determine which of these crashed occurred after an Exit. I suggest that the crash dump summary be enhanced to give this information.l And the summary I save (via cut-and-paste) before I submit each crash report does not give the crash dump ID. For the record, I am running 66.0.5 32-bit on Windows 7, always in safe mode.

Okulungisiwe ngu cor-el

Isicaphuno

Eminye Imininingwane Yohlelo

Fakela amapulagi

  • Shockwave Flash 32.0 r0

Isisebenziso

  • I-ejenti Engumsebenzisi: Mozilla/5.0 (Windows NT 6.1; rv:66.0) Gecko/20100101 Firefox/66.0

Eminye Imininingwane

jscher2000
  • Top 10 Contributor
8642 izisombululo 70690 izimpendulo
Kuphostiwe

Hi Barry, I don't know if anyone here can answer these questions any better than you can.

1) For some reason, Firefox didn't finish shutdown during the allotted time. According to the "App Notes" line, it seems to be related to the "Clear history when Firefox closes" feature:

OMTP- xpcom_runtime_abort(###!!! ABORT: file resource:///modules/Sanitizer.jsm, line 152)

2) The Mozilla Crash Reporter is a separate program (crashreporter.exe) , but I don't know how it is triggered. Conceivably extending the shutdown time has broken some assumption that enables close coordination between the shutdown watchdog process and the crash reporter.

3) If clearing Offline Website Data from time to time completely avoids this problem, that's interesting. However, I don't know how to determine what in particular causes the hang. Perhaps someone familiar with what is being cleared could look at a snapshot of certain files at that point to figure it out.

> Is there a setting so that FF does not save OWD?

I couldn't tell you authoritatively, but if you are experimenting... I notice the preferences related to offline data are named as follows in about:config:

  • privacy.clearOnShutdown.offlineApps
  • privacy.cpd.offlineApps

There's a preference named offline-apps.allow_by_default that you could double-click to toggle from true to false and see whether that makes any difference. I don't know what sites will be affected, but it should be much less problematic than disabling DOM storage.

4) No idea.

Hi Barry, I don't know if anyone here can answer these questions any better than you can. 1) For some reason, Firefox didn't finish shutdown during the allotted time. According to the "App Notes" line, it seems to be related to the "Clear history when Firefox closes" feature: OMTP- xpcom_runtime_abort(###!!! ABORT: file resource:///modules/Sanitizer.jsm, line 152) 2) The Mozilla Crash Reporter is a separate program (crashreporter.exe) , but I don't know how it is triggered. Conceivably extending the shutdown time has broken some assumption that enables close coordination between the shutdown watchdog process and the crash reporter. 3) If clearing Offline Website Data from time to time completely avoids this problem, that's interesting. However, I don't know how to determine what in particular causes the hang. Perhaps someone familiar with what is being cleared could look at a snapshot of certain files at that point to figure it out. > Is there a setting so that FF does not save OWD? I couldn't tell you authoritatively, but if you are experimenting... I notice the preferences related to offline data are named as follows in about:config: * privacy.clearOnShutdown.offlineApps * privacy.cpd.offlineApps There's a preference named '''offline-apps.allow_by_default''' that you could double-click to toggle from true to false and see whether that makes any difference. I don't know what sites will be affected, but it should be much less problematic than disabling DOM storage. 4) No idea.
Ingabe lokhu kube usizo kuwena?
Isicaphuno
Buza umbuzo

Kufanele ulogele ukungena ku-akhawunti yakho ukuze uphendule amaphosti. Uyacelwauqale umbuzo omusha, uma ungekabi nayo i-akhawunti namanje.