Created attachment 568182 [details] firefox-debug_0a2c_2011-10-19_14-41-03-410.log User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.2; Trident/4.0; .NET CLR 1.1.4322; .NET4.0C; .NET4.0E; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729) Steps to reproduce: Started firefox and instantly crashes. Tried running in safe mode and still crashes. Tried creating new profile and still crashes. Uninstalled and reinstalled and still crashes. I started with version 3.0.19 and upgraded to 6.0 and 7.0 and it still crashes. The workstation is on a closed network with no connectivity to the internet but I was able to get a debug report. It's attached Actual results: Continually crashes for anyone that logs into the machine
I guess that this may be a problem with one of your fonts.
How would I go about fixing/removing them?
Use the font entry in the windows system control. You can doubleclick each font and windows should display the font. A font can be broken if windows can't show the text with the font. Just drag&drop the font to a temporary folder to remove the font.You may have to restart windows after removing a font.
Alright I'll try that. Thanks for the quick input everyone.
Ok so I tried each font and windows was able to successfully open each one. Just for S&G's ran firefox again both before and rebooting and it still crashes. Any other ideas?
Could you try creating a brand new Windows user account, and see if it crashes when you run there?
Sure I'll try that. Thanks
Ok tried with a new user account and it still bombs out. Just as an update we do have roaming profiles in our environment. Not sure if that makes a difference or not but when I log in with my account to the workstation it Firefox bombs out but when I use my normal machine it doesn't happen. So it does seem like it's just that workstation.
Anybody else have any suggestions?
Ok I think I figured this one out. I found an article on mozilla.org that mentioned that certain older versions of Spector360 can cause FF to fail on startup so I upgraded the server and clients and that immediately fixed the problem. Thanks for everyone's input.