rocks1985
Apr 22 2006, 22:08
hey, whenever i try to start firefox, i get the following message. but when i check the task manager, there is no firefox process already running and i have tried restarting my computer. any suggestions on how to get firefox up and running? thanks.
primexx
Apr 23 2006, 01:02
ctrl+shift+escape (opens task manager)
click the processes tab
press "f" (no quotes) untill you find "firefox.exe)
right click on firefox.exe
click "end process"
confirm the termination (Press "yes" or something, maybe "ok", forgot)
done.
rocks1985
Apr 23 2006, 01:21
Quote - (primexx @ Apr 22 2006, 21:02) [snapback]587440173[/snapback]
ctrl+shift+escape (opens task manager)
click the processes tab
press "f" (no quotes) untill you find "firefox.exe)
right click on firefox.exe
click "end process"
confirm the termination (Press "yes" or something, maybe "ok", forgot)
done.
but that's the thing...even under the processes tab, there is no firefox.exe running
Circaflex
Apr 23 2006, 01:24
i had this happen once, real annoying because it wasnt in task manager, try restarting first, if it still doesnt work backup your profile and delete the profile folder I think thats what fixed it for me.
ozgeek
Apr 23 2006, 14:37
You sure that Firefox is not shown in Process viewer? Really sure?
Click the "Image Name" header in the process viewer and it will sort all processes by ABC. Scroll down until you see F. Firefox should be around there.
Malik05
Apr 23 2006, 14:52
if u havnt upgraded to the latest firefox, u might wanna do that, cuz i used to have the same problem until i upgraded...
The Champ
Apr 23 2006, 15:56
Quote - (rocks1985 @ Apr 23 2006, 01:21) [snapback]587440198[/snapback]
but that's the thing...even under the processes tab, there is no firefox.exe running
instead of firefox.exe may be mozilla.exe is runnin
supernova_00
Apr 24 2006, 00:12
its probabl talkback.exe that is stuck open, either that or you are running trunk version and using the perl script to analyze crash data and you also have thunderbird open which is still using the nspr.log and that is causing the problem

but I bet its the first part.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.