User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 When browsing, firefox 3.6 will freeze while retrieving anything from the web. All tabs will lock up, not allowing scroll or even redrawing the screen. text in the status bar will show "Transferring foo.jpg from bar.com" -- once foo.jpg is downloaded, the rest of the browser will become responsive again. This also happens if there is a slow response to things like search hint searches, etc. Reproducible: Always Steps to Reproduce: 1.Find a slow network connection 2.Type something into a Google search 3.Wait while you read "Transferring data from www.google.com" Actual Results: Firefox will freeze if web content is not immediately returned. Expected Results: I don't mind so much if one tab waits for content, but I should be able to select other tabs and scroll through their content while I am waiting. Yes, we are having some network issues today. That means I have high latency and some DNS timeouts. The bug is not that content isn't being retrieved, but rather Firefox is locking up the entire UI when content on one tab is slow. This is annoying when that content is something like an advertising web bug. :(
Have you already tried safe-mode / a new profile? http://support.mozilla.com/en-US/kb/Troubleshooting+extensions+and+themes http://support.mozilla.com/en-US/kb/Basic+Troubleshooting#Make_a_new_profile
Version: unspecified → 3.6 Branch
Reporter -> Are you still experiencing this issue? Have you tried safe mode or a new profile?
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
I notice this issue with FF 31. Should I open a new bug or reopen? Can you provide a slow host you tested with successfully to me so I can ty to reproduce?
Further more the 'multi tasking' within FF is not so good, especially noticable when having a few tabs and pages open and then open a page with a lot of flash. Under the hood this may be a a different issue but to the end user the effects are similar: a browser that freezes for no good reason. Ignoring issues like the way this bug was handled is displaying ignorance. A quick look into the code of the relevant part of FF could have shown if indeed some n etwork related code is blocking yes or no. This could have been done in the 3+ years between the developer's comment and now.
udo, it's not terribly helpful to comment in bugs which were closed over 3 years ago. If you have a testcase URL that reproduces the problem with Firefox started in safe mode - http://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode - then please file a new bug
a) bugzilal let me choose this one b) i asked if I could reopen or not c) I asked for a slow website as a reference, not just onet hat I stumble upon occasionally and is not slow all the time d) why would the eternal safe mdoe be involved in basic networking code? we can only conclude if we have a slow reference site.
If a possible fault in basic, core network functionality gets this type of response then yes, we can continue to ramp up the version numbers, but where are the priorities?
You need to log in before you can comment on or make changes to this bug.