User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:22.214.171.124) Gecko/20101026 Firefox/3.5.15 ( .NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:126.96.36.199) Gecko/20101026 Firefox/3.5.15 ( .NET CLR 3.5.30729) I installed and later reinstalled 3.6 when it came out. From then on whenever I exited FireFox, my computer would slow to a crawl. We're talking click the Windows "Start" button and wait 10-15 minutes for the menu to pop up kind of crawl. As I said, I even tried re-installing 3.6 after I figured out what was causing my problems and it still did it. I reinstalled 3.5 and it cleared the problems up. Reproducible: Always Steps to Reproduce: 1.Occurred every time I exited FireFox 3.6.12 2.Tired re-installing to see if maybe it was a problem with the original upgrade. Didn't make any difference at all. 3.Reinstalled 3.5 and it cured problem Actual Results: see above description
Please try the safemode http://support.mozilla.com/en-US/kb/Safe+Mode and a new profile http://support.mozilla.com/en-US/kb/Managing+profiles You could also try Firefox4 Beta7
Reporter, Firefox 4.0.1 has been released, and it features significant improvements over previous releases. Can you please update to Firefox 4.0.1 or later, and retest your bug? Please also create a fresh profile ( http://support.mozilla.com/kb/Managing+profiles), update your plugins (Flash, Java, Quicktime, Reader, etc) and update your graphics driver and Operating system to the latest versions available. If you still continue to see this issue, please comment. If you do not, please close this bug as RESOLVED > WORKSFORME filter: prefirefox4uncobugs
Closing bug as Incomplete - if you are still experiencing this issue or have more information to provide feel free to post back here and we can re-open the bug. You can also get assistance by visiting the Firefox help site -> http://support.mozilla.com/en-US/kb/Ask+a+question
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.