X
Tippen Sie hierhin, um die Version dieser Website für Mobilgeräte aufzurufen.

Hilfeforum

Firefox crashes and does not shut down when closed

Veröffentlicht

Windows 10, Firefox 66.0.1 crashes and does not shut down when closed, with these 2 error messages: 1) Mozilla Crash Reporter (all boxes are checked)

When browser is reopened another error message appears: 2) Close Firefox: Firefox is already running, but is not responding. The old Firefox process must be closed to open a new window.

This appears even after a long delay before restarting Firefox. I have gone through the suggested list of fixes, with no effect.

Crash reports THIS YEAR, older ones date to Feb 2018 : There has been ZERO contact from Mozilla about these reports. bp-a7bc6424-38eb-4584-989e-7d1f80190324 3/24/2019, 12:48 PM View bp-3d058cea-c9e6-475e-bcf3-181390190324 3/24/2019, 12:34 PM View bp-ea5e178b-b5ac-4dcd-9f54-482180190324 3/24/2019, 12:04 PM View bp-df4ec509-cd35-4781-892a-956260190324 3/24/2019, 11:20 AM View bp-68f73f30-afcc-4a4d-905d-d04ae0190324 3/24/2019, 11:08 AM View bp-f2c2eb46-48c5-4c19-b8e1-c8b290190321 3/20/2019, 9:01 PM View bp-ceeb9796-5c8e-49c2-b3d5-842710190317 3/17/2019, 2:21 PM View bp-0229454e-ff31-4c2e-b8b5-ff61e0190317 3/17/2019, 12:53 PM View bp-3c0749fc-5ae3-4270-8caa-f4cc50190316 3/16/2019, 1:27 PM View bp-e6bae4ff-162f-43b4-8c95-add040190316 3/16/2019, 1:15 PM View bp-1af67eef-dd20-41c2-a9ab-20dc30190316 3/16/2019, 10:37 AM View bp-cac7dcac-6905-4047-8168-903df0190316 3/16/2019, 10:21 AM View bp-7ef55f1a-c112-4274-bd5c-e583b0190315 3/14/2019, 9:32 PM View bp-b001c84b-0af8-40b7-9f03-aef040190314 3/14/2019, 6:19 PM View bp-f4ff9526-b972-42a0-8ed5-056780190314 3/14/2019, 7:36 AM View bp-d4ba761f-2b95-4d4e-8d34-ff6fb0190312 3/12/2019, 6:24 AM View bp-e49763df-0553-4add-8663-d6fcd0190311 3/11/2019, 5:20 PM View bp-9fd42285-e5b7-4e4d-840b-527350190311 3/11/2019, 4:56 PM View bp-8573242f-583e-44a9-be8d-abfa90190303 3/2/2019, 7:06 PM View bp-21beab5b-544f-4dea-842f-f26260190301 2/28/2019, 10:38 PM View bp-182b3e0c-04d4-40f5-94ca-1f5a90190301 2/28/2019, 10:08 PM View bp-72db14ff-0ff5-48b8-bb01-e803e0190227 2/26/2019, 7:58 PM View bp-5d905533-7f25-4041-bb20-3602a0190225 2/25/2019, 8:11 AM View bp-b2a6161b-df17-4c92-bd8a-1df390190225 2/25/2019, 8:10 AM View bp-0ac7a875-0eae-4cad-9705-951390190224 2/24/2019, 11:21 AM View bp-ee153af5-da1c-4685-93c4-ab2fa0190223 2/23/2019, 5:55 PM View bp-bd6abde9-a9dd-4364-853c-293390190223 2/23/2019, 5:47 PM View bp-50b03a98-f076-4658-9b56-9326d0190223 2/23/2019, 2:09 PM View bp-b6de254f-259a-4e0e-a64a-24f400190221 2/20/2019, 9:52 PM View bp-1bc0c1a9-4925-4fdf-82e1-2c8fa0190219 2/18/2019, 7:13 PM View bp-6289dca9-bde1-455f-96e9-c84270190217 2/17/2019, 5:29 PM View bp-d3654e50-580b-4455-8faa-9426f0190217 2/17/2019, 4:00 PM View bp-13fa38b6-5ea2-46d5-bd6d-99a880190217 2/17/2019, 3:42 PM View bp-7e975766-9366-43b4-88f0-755ea0190217 2/17/2019, 3:32 PM View bp-10366729-cfa4-4d68-8217-5474f0190217 2/17/2019, 3:27 PM View bp-a44507a2-db63-4571-9800-897c00190217 2/17/2019, 3:23 PM View bp-8e0d3faa-aae2-432b-aca6-afb8b0190217 2/16/2019, 8:31 PM View bp-5605cad2-4bf3-4a75-87fb-fe99f0190216 2/16/2019, 10:48 AM View bp-93d9cb58-669d-4a98-b9f1-ffec50190216 2/15/2019, 10:26 PM View bp-9f763578-dad2-4440-9fc5-2cc3c0190216 2/15/2019, 10:15 PM View bp-ede2137c-6802-416b-9d73-aa5530190216 2/15/2019, 10:15 PM View bp-f0a095e6-4f1c-455d-a15d-31e480190216 2/15/2019, 10:15 PM View bp-9c772a93-0e7c-4e2e-b4f7-e18d30190216 2/15/2019, 10:15 PM View bp-612f308e-4b69-4d4f-b898-d402a0190216 2/15/2019, 10:15 PM View bp-953e7d65-7058-4146-9914-d2ea10190216 2/15/2019, 10:15 PM View bp-fce3816d-8c0d-4f95-81d1-e1b790190216 2/15/2019, 10:15 PM View bp-65ca84ba-c216-4826-a59d-a1dcc0190216 2/15/2019, 10:15 PM View bp-cab01958-987e-4c50-9734-bd2fe0190216 2/15/2019, 10:15 PM View bp-19cbf0f3-37f4-4010-9e4d-c65490190216 2/15/2019, 10:13 PM View bp-b34453c8-f9fa-4616-ae6f-228be0190209 2/9/2019, 3:45 PM View bp-4f30ece9-de33-4de2-8117-cc7be0190207 2/7/2019, 12:28 AM

Windows 10, Firefox 66.0.1 crashes and does not shut down when closed, with these 2 error messages: 1) Mozilla Crash Reporter (all boxes are checked) When browser is reopened another error message appears: 2) Close Firefox: Firefox is already running, but is not responding. The old Firefox process must be closed to open a new window. This appears even after a long delay before restarting Firefox. I have gone through the suggested list of fixes, with no effect. Crash reports THIS YEAR, older ones date to Feb 2018 : There has been ZERO contact from Mozilla about these reports. bp-a7bc6424-38eb-4584-989e-7d1f80190324 3/24/2019, 12:48 PM View bp-3d058cea-c9e6-475e-bcf3-181390190324 3/24/2019, 12:34 PM View bp-ea5e178b-b5ac-4dcd-9f54-482180190324 3/24/2019, 12:04 PM View bp-df4ec509-cd35-4781-892a-956260190324 3/24/2019, 11:20 AM View bp-68f73f30-afcc-4a4d-905d-d04ae0190324 3/24/2019, 11:08 AM View bp-f2c2eb46-48c5-4c19-b8e1-c8b290190321 3/20/2019, 9:01 PM View bp-ceeb9796-5c8e-49c2-b3d5-842710190317 3/17/2019, 2:21 PM View bp-0229454e-ff31-4c2e-b8b5-ff61e0190317 3/17/2019, 12:53 PM View bp-3c0749fc-5ae3-4270-8caa-f4cc50190316 3/16/2019, 1:27 PM View bp-e6bae4ff-162f-43b4-8c95-add040190316 3/16/2019, 1:15 PM View bp-1af67eef-dd20-41c2-a9ab-20dc30190316 3/16/2019, 10:37 AM View bp-cac7dcac-6905-4047-8168-903df0190316 3/16/2019, 10:21 AM View bp-7ef55f1a-c112-4274-bd5c-e583b0190315 3/14/2019, 9:32 PM View bp-b001c84b-0af8-40b7-9f03-aef040190314 3/14/2019, 6:19 PM View bp-f4ff9526-b972-42a0-8ed5-056780190314 3/14/2019, 7:36 AM View bp-d4ba761f-2b95-4d4e-8d34-ff6fb0190312 3/12/2019, 6:24 AM View bp-e49763df-0553-4add-8663-d6fcd0190311 3/11/2019, 5:20 PM View bp-9fd42285-e5b7-4e4d-840b-527350190311 3/11/2019, 4:56 PM View bp-8573242f-583e-44a9-be8d-abfa90190303 3/2/2019, 7:06 PM View bp-21beab5b-544f-4dea-842f-f26260190301 2/28/2019, 10:38 PM View bp-182b3e0c-04d4-40f5-94ca-1f5a90190301 2/28/2019, 10:08 PM View bp-72db14ff-0ff5-48b8-bb01-e803e0190227 2/26/2019, 7:58 PM View bp-5d905533-7f25-4041-bb20-3602a0190225 2/25/2019, 8:11 AM View bp-b2a6161b-df17-4c92-bd8a-1df390190225 2/25/2019, 8:10 AM View bp-0ac7a875-0eae-4cad-9705-951390190224 2/24/2019, 11:21 AM View bp-ee153af5-da1c-4685-93c4-ab2fa0190223 2/23/2019, 5:55 PM View bp-bd6abde9-a9dd-4364-853c-293390190223 2/23/2019, 5:47 PM View bp-50b03a98-f076-4658-9b56-9326d0190223 2/23/2019, 2:09 PM View bp-b6de254f-259a-4e0e-a64a-24f400190221 2/20/2019, 9:52 PM View bp-1bc0c1a9-4925-4fdf-82e1-2c8fa0190219 2/18/2019, 7:13 PM View bp-6289dca9-bde1-455f-96e9-c84270190217 2/17/2019, 5:29 PM View bp-d3654e50-580b-4455-8faa-9426f0190217 2/17/2019, 4:00 PM View bp-13fa38b6-5ea2-46d5-bd6d-99a880190217 2/17/2019, 3:42 PM View bp-7e975766-9366-43b4-88f0-755ea0190217 2/17/2019, 3:32 PM View bp-10366729-cfa4-4d68-8217-5474f0190217 2/17/2019, 3:27 PM View bp-a44507a2-db63-4571-9800-897c00190217 2/17/2019, 3:23 PM View bp-8e0d3faa-aae2-432b-aca6-afb8b0190217 2/16/2019, 8:31 PM View bp-5605cad2-4bf3-4a75-87fb-fe99f0190216 2/16/2019, 10:48 AM View bp-93d9cb58-669d-4a98-b9f1-ffec50190216 2/15/2019, 10:26 PM View bp-9f763578-dad2-4440-9fc5-2cc3c0190216 2/15/2019, 10:15 PM View bp-ede2137c-6802-416b-9d73-aa5530190216 2/15/2019, 10:15 PM View bp-f0a095e6-4f1c-455d-a15d-31e480190216 2/15/2019, 10:15 PM View bp-9c772a93-0e7c-4e2e-b4f7-e18d30190216 2/15/2019, 10:15 PM View bp-612f308e-4b69-4d4f-b898-d402a0190216 2/15/2019, 10:15 PM View bp-953e7d65-7058-4146-9914-d2ea10190216 2/15/2019, 10:15 PM View bp-fce3816d-8c0d-4f95-81d1-e1b790190216 2/15/2019, 10:15 PM View bp-65ca84ba-c216-4826-a59d-a1dcc0190216 2/15/2019, 10:15 PM View bp-cab01958-987e-4c50-9734-bd2fe0190216 2/15/2019, 10:15 PM View bp-19cbf0f3-37f4-4010-9e4d-c65490190216 2/15/2019, 10:13 PM View bp-b34453c8-f9fa-4616-ae6f-228be0190209 2/9/2019, 3:45 PM View bp-4f30ece9-de33-4de2-8117-cc7be0190207 2/7/2019, 12:28 AM
Angefügte Screenshots

Geändert am von subi10

Zitieren

Mehr Details zum System

Installierte Plugins

  • Shockwave Flash 32.0 r0

Anwendung

  • User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0

Weitere Informationen

FredMcD
  • Top 10 Contributor
4224 Lösungen 58965 Antworten
Veröffentlicht

subi10 said

There has been ZERO contact from Mozilla

Crash reports are sent to the Mozilla servers for the techs to look over. They seldom contact the user

''subi10 [[#question-1254139|said]]'' <blockquote> There has been ZERO contact from Mozilla </blockquote> Crash reports are sent to the Mozilla servers for the techs to look over. They seldom contact the user
Hat Ihnen das weitergeholfen?
Zitieren
FredMcD
  • Top 10 Contributor
4224 Lösungen 58965 Antworten
Veröffentlicht

Some reports are too old to be of much use.


Product Firefox Release Channel release Version 66.0.1 Build ID 20190322013140 (2019-03-22) Buildhub data OS Windows 10 OS Version 10.0.17763

Sun, 24 Mar 2019 16:34:11 GMT bp-3d058cea-c9e6-475e-bcf3-181390190324

Sun, 24 Mar 2019 15:25:53 GMT bp-ea5e178b-b5ac-4dcd-9f54-482180190324

Signature: AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize on shutdown

Crash Reason EXCEPTION_BREAKPOINT

VCRUNTIME140.dll = Microsoft Visual C++

IPSEng64.dll = Symantec Intrusion Detection

This is for Sumo's Related Bugs 1524200 REOPENED --- Crash in AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize on shutdown

1507171 RESOLVED FIXED Crash in AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize on shutdown

1426941 RESOLVED INCOMPLETE Crash in AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize on shutdown

1404105 RESOLVED FIXED Crash in AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize,sanitize.js: Sanitize on shutdown

Some reports are too old to be of much use. ------------ Product Firefox Release Channel release Version 66.0.1 Build ID 20190322013140 (2019-03-22) Buildhub data OS Windows 10 OS Version 10.0.17763 Sun, 24 Mar 2019 16:34:11 GMT bp-3d058cea-c9e6-475e-bcf3-181390190324 Sun, 24 Mar 2019 15:25:53 GMT bp-ea5e178b-b5ac-4dcd-9f54-482180190324 Signature: AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize on shutdown Crash Reason EXCEPTION_BREAKPOINT VCRUNTIME140.dll = Microsoft Visual C++ IPSEng64.dll = Symantec Intrusion Detection This is for Sumo's Related Bugs 1524200 REOPENED --- Crash in AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize on shutdown 1507171 RESOLVED FIXED Crash in AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize on shutdown 1426941 RESOLVED INCOMPLETE Crash in AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize on shutdown 1404105 RESOLVED FIXED Crash in AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize,sanitize.js: Sanitize on shutdown
Hat Ihnen das weitergeholfen?
Zitieren
FredMcD
  • Top 10 Contributor
4224 Lösungen 58965 Antworten
Veröffentlicht

It looks like the browser is taking too long to do something. And so it (the watchdog) thinks the browser froze.

Does this happen during normal browsing, during shutdown, reading/watching something, when you walk away . . . . .


Start Firefox in Safe Mode {web link}

A small dialog should appear. Click Start In Safe Mode (not Refresh).

Just let the browser sit there without doing anything. Is the problem still there?

It looks like the browser is taking too long to do something. And so it (the watchdog) thinks the browser froze. Does this happen during normal browsing, during shutdown, reading/watching something, when you walk away . . . . . ----------- [https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode Start Firefox in Safe Mode] {web link} A small dialog should appear. Click '''Start In Safe Mode''' (not Refresh). Just let the browser sit there without doing anything. Is the problem still there?
Hat Ihnen das weitergeholfen?
Zitieren
cor-el
  • Top 10 Contributor
  • Moderator
17415 Lösungen 157335 Antworten
Veröffentlicht

Those crashes are reports about a problem with closing Firefox. Closing takes to long to finish and a crash is forced, so this is more a hang.

Firefox 66.0.1 Crash Report [@ AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize on shutdown ]

Are you using "Clear history when Firefox closes" to clear any personal data like the history?

Those crashes are reports about a problem with closing Firefox. Closing takes to long to finish and a crash is forced, so this is more a hang. Firefox 66.0.1 Crash Report [@ AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize on shutdown ] Are you using "Clear history when Firefox closes" to clear any personal data like the history?
Hat Ihnen das weitergeholfen?
Zitieren
Veröffentlicht

Fragesteller

FredMcD said

subi10 said
There has been ZERO contact from Mozilla

Crash reports are sent to the Mozilla servers for the techs to look over. They seldom contact the user

What is the function of the checked box on the Crash Reprot labeled 'Allow Mozilla to contact me about this report' ?

''FredMcD [[#answer-1207830|said]]'' <blockquote> ''subi10 [[#question-1254139|said]]'' <blockquote> There has been ZERO contact from Mozilla </blockquote> Crash reports are sent to the Mozilla servers for the techs to look over. They seldom contact the user </blockquote> What is the function of the checked box on the Crash Reprot labeled 'Allow Mozilla to contact me about this report' ?
Hat Ihnen das weitergeholfen?
Zitieren
Veröffentlicht

Fragesteller

FredMcD said

It looks like the browser is taking too long to do something. And so it (the watchdog) thinks the browser froze. Does this happen during normal browsing, during shutdown, reading/watching something, when you walk away . . . . .

Start Firefox in Safe Mode {web link}

A small dialog should appear. Click Start In Safe Mode (not Refresh).

Just let the browser sit there without doing anything. Is the problem still there?

The problem occurs only after I shut down the app and try to open again at a later time, sometimes hours later. Once I hit Close Firefox on the 'Already running but not responding' message the browser seems to function normally. I will try the safe mode again, since it was a couple of months age since I tried that.

''FredMcD [[#answer-1207834|said]]'' <blockquote> It looks like the browser is taking too long to do something. And so it (the watchdog) thinks the browser froze. Does this happen during normal browsing, during shutdown, reading/watching something, when you walk away . . . . . ----------- [https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode Start Firefox in Safe Mode] {web link} A small dialog should appear. Click '''Start In Safe Mode''' (not Refresh). Just let the browser sit there without doing anything. Is the problem still there? </blockquote> The problem occurs only after I shut down the app and try to open again at a later time, sometimes hours later. Once I hit Close Firefox on the 'Already running but not responding' message the browser seems to function normally. I will try the safe mode again, since it was a couple of months age since I tried that.
Hat Ihnen das weitergeholfen?
Zitieren
Veröffentlicht

Fragesteller

I reopened in Safe Mode, then closed the browser. Task Manager showed very high power usage of 27.5% for several minutes, then the background processes icons disappeared. Crash Report reappeared as usual.

I reopened in Safe Mode, then closed the browser. Task Manager showed very high power usage of 27.5% for several minutes, then the background processes icons disappeared. Crash Report reappeared as usual.
Hat Ihnen das weitergeholfen?
Zitieren
Veröffentlicht

Fragesteller

cor-el said

Those crashes are reports about a problem with closing Firefox. Closing takes to long to finish and a crash is forced, so this is more a hang. Firefox 66.0.1 Crash Report [@ AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize on shutdown ] Are you using "Clear history when Firefox closes" to clear any personal data like the history?

This had no effect.

''cor-el [[#answer-1207835|said]]'' <blockquote> Those crashes are reports about a problem with closing Firefox. Closing takes to long to finish and a crash is forced, so this is more a hang. Firefox 66.0.1 Crash Report [@ AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize on shutdown ] Are you using "Clear history when Firefox closes" to clear any personal data like the history? </blockquote> This had no effect.
Hat Ihnen das weitergeholfen?
Zitieren
Veröffentlicht

Fragesteller

I am using Norton Security and have Norton Safe Search enabled, no other Add-ons.

I am using Norton Security and have Norton Safe Search enabled, no other Add-ons.
Hat Ihnen das weitergeholfen?
Zitieren
FredMcD
  • Top 10 Contributor
4224 Lösungen 58965 Antworten
Veröffentlicht

subi10 said

What is the function of the checked box

We can't answer that.

subi10 said

I reopened in Safe Mode, then closed the browser.

FredMcD said

Just let the browser sit there without doing anything.

Leave it for a half hour.

Type about:preferences#privacy<enter> in the address bar. The button next to History, select Use Custom Settings.

At the bottom of the page, turn on Clear History When Firefox Closes. At the far right, press the Settings button. Turn on ONLY Cache leaving the others off.

''subi10 [[#answer-1207870|said]]'' <blockquote> What is the function of the checked box </blockquote> We can't answer that. ''subi10 [[#answer-1207882|said]]'' <blockquote> I reopened in Safe Mode, then closed the browser. </blockquote> ''FredMcD [[#answer-1207834|said]]'' <blockquote> Just let the browser sit there without doing anything. </blockquote> Leave it for a half hour. Type '''about:preferences#privacy'''<enter> in the address bar. The button next to '''History, ''' select '''Use Custom Settings. ''' At the bottom of the page, turn on '''Clear History When Firefox Closes. ''' At the far right, press the '''Settings''' button. Turn on ONLY '''Cache''' leaving the others off.
Hat Ihnen das weitergeholfen? 0
Zitieren
Veröffentlicht

Fragesteller

I tried this twice with no effect.

I tried this twice with no effect.
Hat Ihnen das weitergeholfen?
Zitieren
TC Harp 0 Lösungen 1 Antworten
Veröffentlicht

I am only having the 2nd part of this issue. But I have yet to hear of anything that will help this. I get this message each time I try to open the 68.0.2 (64-bit) version, if a window has been recently closed. I sure would like to see a solution to what appears to be a common problem. I don't remember having this problem in the past.

Thank you all,

-TC Harp

I am only having the 2nd part of this issue. But I have yet to hear of anything that will help this. I get this message each time I try to open the 68.0.2 (64-bit) version, if a window has been recently closed. I sure would like to see a solution to what appears to be a common problem. I don't remember having this problem in the past. Thank you all, -TC Harp
Hat Ihnen das weitergeholfen?
Zitieren
Stellen Sie eine Frage

Sie müssen sich mit Ihrem Benutzerkonto anmelden, um auf Beiträge zu antworten. Bitte stellen Sie eine neue Frage, wenn Sie noch kein Benutzerkonto haben.