Firefox 4.0.1 and 3.6.17 hang and cannot be killed on XP w/o reboot
On XP, with Firefox 3.6.17 or 4.0.1, I see frequent loss in connectivity (unrecoverable). This seems associated with network changes (VPN on/off, switch from LAN to wireless broadband, etc.). Once it happens, I can close the (useless) windows, but firefox.exe remains and cannot be killed by Taskmgr or anything else.
It is a very serious issue, since the XP machine often will not even reboot cleanly (but in any case, who wants a browser that requires a frequent system restart?). Please address this, since it basically makes Firefox unusable.
Can't get a crash dump, because firefox.exe will not exit.
All Replies (3)
You should be able to terminate Firefox without rebooting.
- In all Windows systems: Ctrl+Alt+Del then choose Task Manager, then click on the Process tab, select firefox.exe and use the "Del" key or "Terminate Process".
- On Windows 7 (only): Ctrl+Shift_+Esc gets you to the Task Manager quicker.d
Ctrl+Alt+Del has the nickname of "The three finger salute".
Usual things to check for serious problems:
- http://kb.mozillazine.org/Firewalls
- http://kb.mozillazine.org/Problematic_extensions
- http://kb.mozillazine.org/Firefox_hangs
- http://kb.mozillazine.org/Firefox_crashes
Make sure that your Adobe Flash plug-in (10.3.181.22) is up-to-date for Firefox (.
Find updates for installed plugins at mozilla.com/plugincheck
Please read the actual statement. What was not clear about:
cannot be killed by Taskmgr or anything else. ?
When firefox.exe is in this state ONLY A REBOOT can get rid of it. Not taskmgr (tried many times), or even pskill.exe (tried it too).
The issue seems to be related to how Firefox handles the network/proxy (see fix below), and does not seem to happen in IE, ever.
In Tools->Options Advanced tab->Settings Firefox apparently defaults to
Use system proxy settings
and this causes all kinds of issues, including non-killable hangs, in a VPN/multi-network environment. Since I changed to
Auto-detect proxy settings for the network
several days ago, I have seen no problems. This is a welcome fix, since I otherwise really like Firefox, and was moving more and more to IE, which did not have the dead-connection and hang issues described above.