User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Whether I try to open up Firefox by clicking on the shortcut link on my desktop, or I open up a link from within an already opened Firefox page, all of Firefox stops responding for 10-30 seconds. I am not having this problem with IE, so i know that it isnt a problem with my computer/internet connection. I also know that i dont have a virus, any adware, or any spyware. This startd happening two days ago. I have had firefox for quite some time and have never had this problem before. I tried to uninstall and reinstall the software, but it just replicated teh old files. (it was like i had never uninstalled it) Every now and then it will hang too long and cause the program to timeout and force it to end task. Reproducible: Always Steps to Reproduce: 1.Open up Mozilla Firefox from desktop shortcut, or executable in Mozilla Firefox folder. (Bug occurs) 2. Surf the web 3.Open up a link in a new page. (Bug occurs) Actual Results: My Mozilla Firefox becomes unresponsive for 10-30 seconsd. All other open processes work fine. Expected Results: Opened up right away and let me surf the internet without having to wait.
I had exactly the same issue. After removing the proxy extension it now has no delay at all. Hopefully it'll work for you too. I think the first time this happened it lasted a couple of days and the way I got around it that time was to choose the 'safe mode' from the start menu. Fingers crossed that it's cured this time.
I got the lag down to less than a second, so now it isnt that annoying. Hopefully when I restart my comp that lag will go away too. :)
Uninstalling Switch proxy seems to have cured my problems too. Shame it was a great tool and has worked well until recently. No doubt another Microsoft patch has interfered.
I have narrowed down the problem to the autoupdate feature of the SwitchProxy tool. When I turned this off, the problem went away. Probably the server was down because the website was unaccessible as well. Now there is a new website up. So in short, this was not a firefox bug at all.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.