Why is FF 5.0 crashing every time I merely open it?
Every time since I've upgraded to the new 5.0 version that I open Firefox, whether I leave it open with no tabs or websites up or if I go to a website it crashes. I've tried to access my crash reports to give you guys more details but after multiple attempts it won't stay open long enough for me to access it.
I've looked to see if I could downgrade to the older version that worked fine for me but couldn't find it.
I'm running it on a MacBook Pro with Mac OS X 10.6.8 software.
All Replies (1)
I just discovered it was RealPlayer that was crashing my Firefox, even when RealPlayer wasn't running!
On a whim, I installed RealPlayer on my system yesterday, which is such monstrous bloatware, it was like installing a new spinal column. The damage was not evident until I shut down the computer and restarted it again this morning. Then starting up Firefox was like slamming repeatedly into a stone wall. Bring it up and immediate crash, bring it up and immediate crash. I tried uninstalling and reinstalling FF 5.0, no luck. So I backed up to FF 4.0, SAME THING.
It took me all d*mn day to track this thing down, and I'm quite angry about it. Not only did RealPlayer mess up my Firefox, it disabled my Windows System Restore. When I finally got RealPlayer uninstalled, it told me it cannot delete certain files until I restarted the system, did I want to see the files. Of course I said yes. Here is the list:
The following files and/or directories could not be deleted:
C:\Documents and Settings\All Users\Application Data\Real\RealPlayer\BrowserRecordPlugin\MozillaPlugins\nprpchromebrowserrecordext.dll C:\Documents and Settings\Suzanne\Application Data\Real\RealPlayer c:\program files\real\realplayer c:\program files\real\realplayer c:\program files\real c:\program files\real\realplayer\Update C:\Documents and Settings\All Users\Application Data\Real\RealPlayer\BrowserRecordPlugin\MozillaPlugins
I do believe from this it was RealPlayer inviting itself to be a browser plugin for me, that is the source of the problem. Not anymore. I ripped it out by its roots, and its back to all open source players for me.
(I am happily writing this reply from Firefox 5.0)
Modified