Firefox doesn't close completely
Since v.62 upgrade, Firefox appears to be failing to close completely. When I examine Task Manager under "Processes," I note remnants of Firefox remaining. After I close Firefox and later attempt to reopen, I receive a box warning me that I need to close Firefox before opening it again. So, I click on the "Close" option and then the next session opens. Any idea why Firefox is beginning to leave a little of itself behind preventing a window to be opened again? Is there something I need to do different in configuration of v.62 that I didn't do in previous versions? I run a PC with Windows10 Home v.1803, latest updates installed, AMD A10-5700 processor, 12G RAM, 2TB hard drive.
Thanks for the help & advice. Rick
All Replies (6)
hi, if you let the firefox process sit for 60 seconds after you've closed the browser interface there should be a mechanism kicking in that force closes the browser and generates a crash report. do you see that crash reporter window if you wait for it? if yes could you please submit the report, then go to about:crashes, scroll down to the section of submitted reports and copy/paste the crash report's id (starting with bp-) here into a reply - perhaps this contains some information of what's going wrong... thank you
I have the same Problem please need help.. Every time i close firefox, all the Processes still open ... I have to manually close it by using ctrl+alt+del by opening the task manager and killing one by one usually have like 4 or 5 opened. I using last version 62.0.3
I dont get any crash report windows,, but i search for it in the help windows and get many crash reports : i post u the last 2 days
https://crash-stats.mozilla.com/report/index/591fd110-2e86-4dc4-9e78-a4d070181008#tab-details
https://crash-stats.mozilla.com/report/index/94d15f66-c6e9-4914-b0f3-4cb970181008
thank you, there isn't an immediate cause apparent in those two reports. have you set firefox to clear parts of your history within the options > privacy/security panel?
also the reports show that a module named gemmauf32.dll on your system is hooking into the browser process - googling for it turns up 0 results which is quite unusual. you might want to look into that and see where the file is placed on your harddrive and if it belongs to a legitimate software...
Thanks for the help Philipp. You are correct, after some amount of time passes, it appears lingering elements are removed and Firefox reopens w/o trouble - at least for me. I haven't experimented with timing, just gave it 5-8 minutes while I did something else and reopened the program. Appreciate the advice.
Try to use one of these to close Firefox if you are currently doing that by clicking the close X on the Firefox title bar.
- "3-bar" menu button -> Exit (Power button)
- Windows: File -> Exit
- Mac: Firefox -> Quit Firefox
- Linux: File -> Quit
Boot the computer in Windows Safe mode with network support to see if that has effect in case other software is causing problems.
- http://www.bleepingcomputer.com/tutorials/how-to-start-windows-in-safe-mode/
- http://www.7tutorials.com/4-ways-boot-safe-mode-windows-10
@ Zyko17
The crash reports show a rather low number for the available virtual memory, so maybe you should increase the size of the page file.
- memoryMB : 3575 (normal for 32-bit OS)
- virtualMaxMB : 2048