Firefox 9.0.1 Hangs and Crashes Regardless of Website, WebContent, Extensions, Etc
I have checked through the support forums and googled this issue, but have seen no resolve for my particular case.
It should be noted that I'm using a corporate laptop that I have admin rights to, but don't have control over windows update, McAfee security software, and a few other items. The hard drive is encrypted as well using McAfee Endpoint Encryption.
Firefox 8.0.1 works like a charm, and all versions before that have worked perfectly fine. However, when Firefox automatically updates to 9.0.1, I lose all functionality. Upon install, it will hang on the "checking extensions" dialog box typically within a theme. I can close out of the dialog, and firefox will launch. However it just hangs. Nothing will happen at all. Websites won't come up, I can get into some menu items, but typically cannot alter anything (such as in Tools > options. I might make a change, but it will never take).
Regardless of how I then close Firefox, the process continues to run (I've let this go as long as 2 hours and then had to kill the task in task manager).
When I restart one of two things will happen. Typically A) it hangs as described above or B) a website may load (such as when I click on a link in an email or office document, but when I attempt to navigate (click on a link within the website) or even scroll down the page, firefox will promptly crash.
I found an old version of 8.0.1 online and was successful in reinstalling it. Everything works like a charm in 8.0.1. I updated ALL of my extensions, and disabled all add-ons. I cleared everything possible. I even disabled hardware acceleration. Typically by the time I close out of firefox and open it a second time, 9.0.1 would have automatically downloaded and initiated install, so then I have to kill the process and re-install 8.0.1 manually to regain functionality.
And yes, these things occur in safe mode as well. When updated to 9.0.1 not only are options unable to be changed, but attempting to get into about:crashes or about:config fails.
I also attempted to download the FireFox 10 beta, which yields the same result.
Any insight would be more than appreciated. Clearly it appears that some function available within FireFox 9.0.1 which was not the same in 8.0.1 is causing this issue.
As an aside, a colleague of mine was having the same issue and reverted to our company's internal software library that is still using FireFox 4.0.0.
すべての返信 (7)
You have pointed quite a couple of issues. Perform the suggestions mentioned in the following articles:
- Run as Administrator
- Firefox hangs or is not responding - How to fix
- Troubleshoot Firefox crashes (closing or quitting unexpectedly)
- How to fix preferences that won't save
Check and tell if its working.
No. Those are separate issues. I have attempted individual resolve, but for the most part, I have absolutely no functionality when updated to FireFox 9.0.1 or 10.0. None of the individually will fix my issue, which is a combination of all of them. Even with the update to FireFox 10.0, I'm having the same problems.
-> Restart your System in Safe Mode
-> Uninstall your current Firefox => Uninstall Firefox from your computer
- DO NOT SELECT TO REMOVE USER DATA AND SETTINGS
- Restart your system
-> Do a MALWARE check with these Malware Scanning programs. You need to scan with all programs because each program detects different malware. Make sure that you UPDATE each program to get the latest version of their Databases before doing a Scan. Also, Close All other Applications (softwares) before Starting to Run Scans.
- Malwarebytes' Anti-Malware -> http://www.malwarebytes.org/products/malwarebytes_free
- SuperAntispyware -> http://www.superantispyware.com
- Ad-Aware Free Internet Security -> http://www.lavasoft.com/products/ad_aware_free.php
- Spybot Search & Destroy -> http://www.safer-networking.org/en/index.html
- Anti-Rootkit Utility TDSSKiller -> http://support.kaspersky.com/faq/?qid=208283363
-> How to install Firefox on Windows
Check and tell if its working.
この投稿は Hasan により に変更されました
I appreciate your response, however it is not spyware/malware related. As stated previously, it's a corporate laptop. I'm behind a proxy which keeps me off any websites that could even be slightly malicious. On top of that, I run a script blocker, and ad-blocker, and my laptop has never been used for anything other than business purposes (read, I don't use any rogue software or websites). And as an aside, I work for the Army National Guard in an IT role. I understand how to keep my machine clean and free from virus/spyware/malware.
Even further, I have no issues whatsoever with IE, Chrome or previous versions of FireFox, which in my experience would also be affected by rogue software.
Thanks for trying.
Your Crash Report is -> https://crash-stats.mozilla.com/report/index/50ba6fa5-48b6-4f30-bd38-b31af2120123
Seeing that your extensions were running & enabled when your Firefox Crashed, perform the suggestions mentioned in the following articles:
- Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems
- Troubleshoot issues with plugins like Flash or Java to fix common Firefox problems
Check and tell if its working.
この投稿は Hasan により に変更されました
Just as an aside, I wonder if your corporation or whatever is now aware that Firefox now has Firefox ESR. ([Enterprise] Extended Support Release) I wonder if your corporation is aware of this, as an IT professional yourself you may be interesting in drawing this to the attention of your company see https://wiki.mozilla.org/Enterprise
It is possible your Company may wish to consider using that rather than the unsupported Firefox 4.
I am guessing the crash and so maybe also the hangs relate to the use of McAfee software. Looking at the Crash ID report already linked by mha007 above I note a Bug has recently been filed regarding bugs with your crash signature:
- Signature: rand_s
- Bug 723447 - Crash in ChildProcessInfo::GenerateRandomChannelID @ rand_s with McAfee Host Intrusion Prevention
The fastest solution may come from contacting your own IT department and pointing out the problem to them and mentioning the bug report that has been filed.