Firefox always crashes on exit
Not sure when it began, probably before the current version, i.e. it's not related to the latest update. When exiting, everything seems fine at first but then Crash Reporter pops up. If I try to restart my Windows/PC with FF open, the restarting becomes blocked by Firefox, so I have to cancel the restart and deal with Crash Reporter first.
The same crash happens in Troubleshoot Mode.
I don't have any special security software (aside from Malwarebytes with real-time protection disabled).
Latest reports: bp-3e00592e-2756-43bf-9642-01b550220502 bp-2435de7c-8279-4d85-b151-b94380220502
Signature is different (almost) every time but as far as I remember no crash felt any different from the two crashes above. For example: bp-093ec6db-d0e2-4f05-8dbd-e03b50220429 bp-47c1b14c-cba2-4007-9f53-089fc0220429 bp-f4ca1090-d760-4209-a47f-8d40e0220429 bp-4a506f38-75ac-4f62-b4bc-324f00220429 bp-d9a19762-4234-450e-82ed-d41940220429 bp-1b0e9da0-29e6-4107-ad7e-ed77f0220429
Выбранное решение
When the browser shuts down, do you have it set to remove a lot of data? Sometimes the data removal can cause problems when there is a lot of data to clear.
Type about:preferences#privacy<enter> in the address box.
The button next to History, select Use Custom Settings.
Turn on Remember My Browsing And Download History 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 and Form And Search History leaving the others off.
Прочитайте этот ответ в контексте 👍 1Все ответы (5)
The other reports are too old to be useful
bp-3e00592e-2756-43bf-9642-01b550220502 bp-2435de7c-8279-4d85-b151-b94380220502 Signature: AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize on shutdown
MOZ_CRASH Reason (Sanitized) : [Parent 16400, Main Thread] ###!!! ABORT: file resource:///modules/Sanitizer.jsm:168
Crash Reason EXCEPTION_BREAKPOINT
This is for Sumo's Related Bugs 1578273 NEW --- Firefox process staying alive after exit
1524200 RESOLVED FIXED 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 REOPENED --- 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 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ bp-47c1b14c-cba2-4007-9f53-089fc0220429 Signature: shutdownhang | XPTC__InvokebyIndex
MOZ_CRASH Reason (Sanitized) : Shutdown hanging at step profile-change-teardown. Something is blocking the main-thread.
Crash Reason EXCEPTION_BREAKPOINT
This is for Sumo's Related Bugs 1442971 NEW --- Crash in shutdownhang | XPTC__InvokebyIndex ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Product Firefox Release Channel release Version 99.0 Build ID 20220330194208 (2022-03-30)
bp-093ec6db-d0e2-4f05-8dbd-e03b50220429 Signature: shutdownhang | NtUserMsgWaitForMultipleObjectsEx | nsAppShell::ProcessNextNativeEvent
MOZ_CRASH Reason (Sanitized) : Shutdown hanging at step profile-change-teardown. Something is blocking the main-thread.
Crash Reason EXCEPTION_BREAKPOINT
This is for Sumo's Related Bugs 1588498 ASSIGNED --- [meta] Remaining issues that may cause QuotaManager shutdown hangs
Изменено FredMcD
Выбранное решение
When the browser shuts down, do you have it set to remove a lot of data? Sometimes the data removal can cause problems when there is a lot of data to clear.
Type about:preferences#privacy<enter> in the address box.
The button next to History, select Use Custom Settings.
Turn on Remember My Browsing And Download History 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 and Form And Search History leaving the others off.
Basically, an OOM (Out Of Memory) means the system is having issues with the RAM.
https://support.mozilla.org/en-US/kb/firefox-slow-how-make-it-faster
https://support.mozilla.org/en-US/kb/firefox-uses-too-many-cpu-resources-how-fix
https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-ram
https://support.mozilla.org/en-US/kb/firefox-hangs-or-not-responding
https://support.mozilla.org/en-US/kb/firefox-takes-long-time-start-up
https://support.mozilla.org/en-US/kb/quick-fixes-if-your-firefox-slows-down
https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-or-cpu-resources
MemTest
Could you please run a tool from http://memtest.org/
in order to check the integrity of your RAM?
You will need a thumb or disk drive to install it on.
Do you let Windows handle the page file or did you set a fixed size ?
Control Panel -> System -> Advanced -> Performance -> Settings
If you use a fixed size for the page file then try the former and let Windows handle the page file. How to determine the appropriate page file size for 64-bit versions of Windows {web link}
I had the same issue. It seemed to be related to clearing recent history (using 'Everything' as the time range) so, in the second profile I created, I avoided doing that and instead I now select 'Today' in clear recent history (ctl+shft+del). I was warned about the custom history option "Clear history when Firefox closes" so I don't use that.
MemTest didn't find anything. Page file was already set to purely automatic.
about:preferences#privacy seems to work. I didn't close the browser for two weeks, then closed it, no crash.