How it all started...
I just had an crash with firefox and thought, oh well just start it again.
Then I see by the looks of the cursor windows is doing something, but firefox won't start.
I checked the task manager > processes list and it started but no new taskbar icon and the memory was very low like 3-4MB.
I killed it and tried to start in safe mode with the -safe-mode tag, it results in the same thing, it starts the process and it stalls.
Same for the -profilemanager tag.
I then got the latest version of firefox and installed it over the old on.
Which apparently did nothing since I still got the same results, it won't start.
I uninstalled en reinstalled which also didnt help and moved my old profile over so it would create a new one which still did not allow firefox to start.
I then renamed firefox.exe to firefox2.exe and it started all fine.
I know I have firefox.exe proxified via a program called Proxifier (http://www.proxifier.com/).
I saw in proxifier that firefox was trying to connect to 127.0.0.1 at some random ports.
Which I thought was strange, then I loaded up Process Explorer (http://www.sysinternals.com) and checked the TCP/IP part of the firefox and saw it was was trying to connect to activate.adobe.com.
Which I have in my HOSTS file for some reason...
Hence proxifier was connecting to my localhost and thus stalled firefox.
But why does it have to connect to activate.adobe.com in the first place?
If it's because of a plugin from adobe, shouldn't it be disabled when I run the firefox safe mode.
I've been using proxifier + my current HOSTS file for a long time why is this the first time I'm having troubles with it.
I know firefox was bugging me with a new update but I'm pretty sure I said "Not now".
If someone can enlight, please do, thanks!
Running Windows 7 with Firefox 3.6.7