Firefox process runs after close for more than five minutes.
I'm seeing this on a lot of Windows Vista and 7 computers. I close Firefox (with the X in the top right) but the firefox.exe process continues to run for 5+ minutes and if I try to start it again, I get the "Firefox is already running" message. Sometimes if I wait long enough, I get a FF crash.
Is there an easy way to post the crash logs from various computers?
Firefox also seems to take a long time to open websites (Chrome and IE work fine).
All of these computers have been scanned for infections with: Malwarebytes, Sophos, NOD32, ADWcleaner and JRT.
Some of them already had FF 43 on them, some are new installs of 44.
What I've tried so far: 1)Uninstalled Firefox, removed all folders and Mozilla entries in HKCU and HKLM and reinstalled - no change. 2)Updated video drivers to latest versions - no change. 3)Checked permissions on Profile Folder - these were correct. 3)Ran an in-place upgrade or repair install - this seems to fix the problem.
I'm hoping there's an easier fix for this than an in-place upgrade. Any suggestions would be greatly appreciated.
Thanks for any help?
All Replies (6)
I tried creating an entirely new Windows profile, but the problem exists in the new profile as well.
I also did an SFC /scannow with now change, and I've tried disabling HW acceleration.
I really need a fix for this. Surely I'm not the only one having the problem.
You asked, "Are there instructions on deciphering crash logs?"
I tried googling some of the titles (signatures) of your crash reports, for example "Firefox 44.0 Crash Report [@ shutdownhang | WaitForSingleObjectEx | WaitForSingleObject | PR_WaitCondVar | nsThread::ProcessNextEvent | NS_ProcessNextEvent | nsThread::Shutdown ] ." When you do this, Google will find pages such as "2015-10-01 Firefox 44.0a1 on Windows 8 Top Crash Report" https://crash-analysis.mozilla.com/rkaiser/2015-10-01/2015-10-01.firefox.44.0a1.win8.topcrash.html . On these pages, you can search for your exact crash report and find information on it, for example which bug is responsible for it. I haven't found any useful information on the particular crash signature above, so far. I'll do some more searching tomorrow. Keep in mind that I'm a total amateur at this. I'm not sure how helpful this actually is. At least it's something we can do.
Athraithe ag user1312655 ar
You can click a crash report item on the about:crashes page to go to the Mozilla Crash Reports website.
If you can't open Firefox, see:
Well, I can add yet another Windows 7 computer to the list of computers affected (that's five Windows 7 and three Vista).
Hopefully someone has an idea how to fix this.
I have improved stability and speed a bit by disabling both DNS Client and DHCP client services (which forces me to use a static IP address) on a Windows 7 PC. At this point pages are loading within 3 to 5 seconds (still slower than Chrome but better than the 15 to 60 seconds it was taking). I don't seem to be getting crash reporter every time I exit now, but the process still takes 30 seconds to 2 minutes to stop after I close Firefox.
brundleflyguy said
I'm seeing this on a lot of Windows Vista and 7 computers. I close Firefox (with the X in the top right) but the firefox.exe process continues to run for 5+ minutes and if I try to start it again, I get the "Firefox is already running" message. Sometimes if I wait long enough, I get a FF crash. Is there an easy way to post the crash logs from various computers? Firefox also seems to take a long time to open websites (Chrome and IE work fine). All of these computers have been scanned for infections with: Malwarebytes, Sophos, NOD32, ADWcleaner and JRT. Some of them already had FF 43 on them, some are new installs of 44. What I've tried so far: 1)Uninstalled Firefox, removed all folders and Mozilla entries in HKCU and HKLM and reinstalled - no change. 2)Updated video drivers to latest versions - no change. 3)Checked permissions on Profile Folder - these were correct. 3)Ran an in-place upgrade or repair install - this seems to fix the problem. I'm hoping there's an easier fix for this than an in-place upgrade. Any suggestions would be greatly appreciated. Thanks for any help?