X
Thinta lapha ukuze uye kuveshini yamakhalekhukhwini kusayithi.

Isithangami Sabeseki

Lolu chungechunge lwavalwa lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Firefox 65 shows crash AFTER it's completely shutdown

Kuphostiwe

Version 65 is working fine, but every time I shut it down, the crash notice comes up AFTER the last process closes. In other words, the crash shows up when no Firefox processes are running (as displayed by Process Explorer). Other than that, everything is just fine, but this message is just annoying. One other thing: If I manually kill the last process, the crash message does NOT show up. As I said, nothing bad is happening, but this is annoying.

Version 65 is working fine, but every time I shut it down, the crash notice comes up AFTER the last process closes. In other words, the crash shows up when no Firefox processes are running (as displayed by Process Explorer). Other than that, everything is just fine, but this message is just annoying. One other thing: If I manually kill the last process, the crash message does NOT show up. As I said, nothing bad is happening, but this is annoying.

Isisombululo esikhethiwe

thank, can you try if the following step is making a difference: press ctrl+shift+del in firefox to bring up the dialog to clear recent history, select the time range "everything", untick all boxes except "offline website data" and let firefox clear that. does firefox shut down cleanly after that?

Funda le mpendulo ngokuhambisana nalesi sihloko 1

Eminye Imininingwane Yohlelo

Fakela amapulagi

  • Shockwave Flash 32.0 r0

Isisebenziso

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

Eminye Imininingwane

philipp
  • Top 25 Contributor
  • Moderator
5324 izisombululo 23512 izimpendulo
Kuphostiwe

hi luckystarr, thanks for reporting this problem. could you also provide your latest few submitted crash reports? please enter about:crashes into the location bar, copy the latest few report ids from there starting with bp- & paste them here into a forum reply. this will give us a better understanding what may be triggering those crashes. thank you :))

hi luckystarr, thanks for reporting this problem. could you also provide your latest few submitted crash reports? please enter '''about:crashes''' into the location bar, copy the latest few report ids from there starting with '''bp-''' & paste them here into a forum reply. this will give us a better understanding what may be triggering those crashes. thank you :))

Umnikazi wombuzo

I haven't been submitting them since the first couple of them.

bp-f77fa6f8-637c-4e33-a48a-ca3b40190201 bp-d8d2f582-cc04-4e58-8089-04b040190204

The second one was in the unsubmitted section, so I went ahead and submitted it. What's interesting is that there are only two, but I know I've had more crash messages than that. I ran into a problem (mucking with the registry) trying to see if another issue I had was the problem. I had to do a restore to fix that so I may have lost some others. Hope this helps.

I haven't been submitting them since the first couple of them. bp-f77fa6f8-637c-4e33-a48a-ca3b40190201 bp-d8d2f582-cc04-4e58-8089-04b040190204 The second one was in the unsubmitted section, so I went ahead and submitted it. What's interesting is that there are only two, but I know I've had more crash messages than that. I ran into a problem (mucking with the registry) trying to see if another issue I had was the problem. I had to do a restore to fix that so I may have lost some others. Hope this helps.
philipp
  • Top 25 Contributor
  • Moderator
5324 izisombululo 23512 izimpendulo
Kuphostiwe

Isisombululo Esikhethiwe

thank, can you try if the following step is making a difference: press ctrl+shift+del in firefox to bring up the dialog to clear recent history, select the time range "everything", untick all boxes except "offline website data" and let firefox clear that. does firefox shut down cleanly after that?

thank, can you try if the following step is making a difference: press ctrl+shift+del in firefox to bring up the dialog to clear recent history, select the time range "everything", untick all boxes except "offline website data" and let firefox clear that. does firefox shut down cleanly after that?

Umnikazi wombuzo

BINGO! I neglected to mention that I had the problem on another PC as well. I tried the fix on that one first, and it worked.! So I went back to my main machine, and that one behaved properly as well. Thanks for a solution and for being so prompt.

BINGO! I neglected to mention that I had the problem on another PC as well. I tried the fix on that one first, and it worked.! So I went back to my main machine, and that one behaved properly as well. Thanks for a solution and for being so prompt.
emmryss 0 izisombululo 9 izimpendulo
Kuphostiwe

I have this same problem but erasing all my history seems a little drastic. Is there anything else one can do?

I have this same problem but erasing all my history seems a little drastic. Is there anything else one can do?
cor-el
  • Top 10 Contributor
  • Moderator
17591 izisombululo 159130 izimpendulo
Kuphostiwe

This is not about clearing the browsing history, but about clearing local storage (IndexedDB): untick all boxes except "offline website data"

This is not about clearing the browsing history, but about clearing local storage (IndexedDB): ''untick all boxes except "offline website data"''
bsfinkel 1 izisombululo 192 izimpendulo
Kuphostiwe

I have the same problem. Most of the time when I Exit Firefox, the crash report occurs AFTER the firefox.exe process has ended. But not the time I did an Exit about 20 minutes ago. I do not understand why the suggestion above "clearing local storage (IndexedDB)" resolves the problem. Is this a work-around for a code deficiency? I do not know how a crash report can be created after a process has terminated. I have had the occurrence when I exit Firefox, see that the process has ended (via Task Manager), restart Firefox, and then get the crash report. When this happens, I have to "play games" to get the crash report sent.

The more important problem (which maybe should be another trouble ticket( 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-470cb28b-9389-4e85-bf84-643240190520 5/20/2019 9:53 AM 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-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

I have the same problem. Most of the time when I Exit Firefox, the crash report occurs AFTER the firefox.exe process has ended. But not the time I did an Exit about 20 minutes ago. I do not understand why the suggestion above "clearing local storage (IndexedDB)" resolves the problem. Is this a work-around for a code deficiency? I do not know how a crash report can be created after a process has terminated. I have had the occurrence when I exit Firefox, see that the process has ended (via Task Manager), restart Firefox, and then get the crash report. When this happens, I have to "play games" to get the crash report sent. The more important problem (which maybe should be another trouble ticket( 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-470cb28b-9389-4e85-bf84-643240190520 5/20/2019 9:53 AM 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-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

Okulungisiwe ngu cor-el

cor-el
  • Top 10 Contributor
  • Moderator
17591 izisombululo 159130 izimpendulo
Kuphostiwe

Hi Barry.

Your crash is likely different then what this thread is about, so could you please create a new thread (the original poster will receive mails from replies in this thread)?

Thanks.

(locking)

Hi Barry. Your crash is likely different then what this thread is about, so could you please create a new thread (the original poster will receive mails from replies in this thread)? Thanks. ''(locking)''

Okulungisiwe ngu cor-el