Closed
Bug 469459
Opened 16 years ago
Closed 14 years ago
Firefox hangs after resuming from Hibernation
Categories
(Core :: Networking, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: bram.ridder, Unassigned)
References
Details
(Keywords: hang, Whiteboard: [see comment 28])
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.1b2) Gecko/20081201 Firefox/3.1b2
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.1b2) Gecko/20081201 Firefox/3.1b2
Ever since I downloaded the new Firefox 3.1b2, the browser hangs whenever I shut the lid of my iBook G4 (running Mac OS X 10.4.11) and reopening it when Firefox is opened is will simply hang for a very long time (I'm always forced to use force quit and reopen the application before I can continue browsing).
I've had this situation with different web pages, so it doesn't seems to be confined to a certain web page.
- Bram
Reproducible: Always
Steps to Reproduce:
1. Open any web page (say youtube.com).
2. Shut the lid of your MacBook / iBook and let it go into hibernation.
3. Open it up again.
Actual Results:
Firefox will hang, its unresponsive and you'll see the colourful turning wheel until you force quit Firefox and restart it.
Expected Results:
It shouldn't hang.
I haven't tried Firefox 3.1b1, so I'm not sure if this bug was already present there. It wasn't in the 3.0 branch in any case.
Comment 1•16 years ago
|
||
Tested on Windows XP with the latest trunk build and the latest plugin version I saw a minor problem with the sound, but this could be a bug in the plugin. No hang in any case so it might be Mac-only.
Do you have the latest flash version and to rule out bugs in extensions, can you also reproduce it in safe-mode?
http://support.mozilla.com/en-US/kb/Safe+Mode
Reporter | ||
Comment 2•16 years ago
|
||
I've ran Firefox in safe mode and disabled all plugins and I get the same results. I closed my iBook, went to sleep and the next morning when I opened it again Firefox simply hang...
Comment 3•16 years ago
|
||
I can't reproduce this. I tested today's Minefield and Shiretoko nightlies in OS X 10.4.11 on an early model MacBook Pro.
I loaded my favorite YouTube video (http://www.youtube.com/watch?v=TZ860P4iTaM&NR=1), and closed my MacBook Pro's cover while it was playing. It went to sleep (and the video stopped playing) after a few seconds. Then 30 minutes later I opened the cover, the computer woke up, and the video picked up where it had left off.
I had no problems at all.
Reporter | ||
Comment 4•16 years ago
|
||
Steven:
Try to leave Firefox open overnight while your Mac is hibernating. One instance that always work is:
1) Open gmail
2) Close *Book
3) Go to sleep
4) Open *Book
5) Click any message and Firefox will hang.
Could you please try that?
Comment 5•16 years ago
|
||
I can see this too with Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b3pre) Gecko/20081229 Shiretoko/3.1b3pre ID:20081229020258. The only difference is that I don't get the beach ball.
Probably this issue is based on DNS resolving. I always happens to me even after some seconds in hibernation mode. After I wake up my MacBook it takes about 3-4 minutes until I'm able to load some pages. That's really annoying.
Given Gmail as example is a good way to reproduce. While it is using Ajax the UI doesn't response for a very long time. I believe that everyone on OS X should be able to see it. I'll try if I can reproduce it on Windows too by tomorrow.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Hardware: PowerPC → All
Version: unspecified → Trunk
Comment 6•16 years ago
|
||
I can try this in the lab with one of the Mac machines as well to see what happens.
Comment 7•16 years ago
|
||
(In reply to comment #4 and comment #5)
I can't reproduce the STR from comment #4, or what Henrik describes in
comment #5. But here's something I *can* reproduce ... though only on
OS X 10.5.6 (not on OS X 10.4.11):
1) Visit https://mail.google.com/ and log in.
2) Close your laptop (in my case an early model MacBook Pro) -- to
make it sleep.
3) Open your laptop -- to wake it up.
4) Click on the "Sign out" button (in the upper right).
If I'm running on OS X 10.5.6, there's always a 10-15 second delay
at this point (before the log in page reappears).
I don't see this delay if I skip steps 2 and 3.
If it makes any difference, my MacBook Pro has an ethernet connection
(and a fixed IP address -- i.e. it's not using DHCP).
Comment 8•16 years ago
|
||
These are not only some seconds. Clicking the inbox after wakeup it takes more than a minute and even reloading the whole page and other tabs doesn't help. I cannot be caused by DHCP because other apps still work.
Comment 9•16 years ago
|
||
(In reply to comment #8)
As I've said, I can't reproduce what you report :-)
Comment 10•16 years ago
|
||
Actually, Henrik, I've now seen something a bit more like you describe
-- though once again only on OS X 10.5.6 (not on 10.4.11).
Here's a precise STR:
1) Visit https://mail.google.com/ and log in.
2) Click on some other mailbox than Inbox (e.g. Spam).
3) Close your laptop -- to make it sleep.
4) Open your laptop -- to wake it up.
5) Click on Inbox -- it displays without delay.
6) Click on the "Sign out" button (in the upper right).
After a long delay (at least a minute or two), you get a network
timeout error. Once you retry everything is fine.
If you try to reload the page before the timeout you get an error
page from Google. If you just try to revisit
https://mail.google.com/ (before the timeout), you get a Redirect
Loop error page.
Comment 11•16 years ago
|
||
Boris or Biesi, which type of log would be helpful to narrow down this problem? Will this be visible with a simple HTTP log?
Comment 12•16 years ago
|
||
Hmm. I don't know offhand.
Is the CPU pegged during this time? If so, a shark profile would at least tell us where the time is spent. If not (as in, we're waiting on i/o or something), life's harder... You could try reproducing under a debugger and then breaking while the browser is unresponsive, to see which things we're waiting on, perhaps?
Comment 13•16 years ago
|
||
Personally I feel that it's much better with the patch on bug 467562 checked-in. Bram and Steven, can you both verify the improvement?
Comment 14•16 years ago
|
||
(In reply to comment #13)
So do I.
I tested my STR from comment #10 in today's Minefield and Shiretoko nightlies, and I can't reproduce it anymore. (I did once see a long delay at step 6, but not either of the error pages.)
Comment 15•16 years ago
|
||
(Following up comment #14)
But now I can't reproduce my comment #10 STR with the 2009-01-06 nightlies, either.
Google must have silently changed their site.
Reporter | ||
Comment 16•16 years ago
|
||
I'll test the last nightly ASAP and let you guys know. thanks!
Reporter | ||
Comment 17•16 years ago
|
||
(In reply to comment #16)
> I'll test the last nightly ASAP and let you guys know. thanks!
I can't reproduce the bug in the latest trunk version of Firefox, so I think it is fixed with the latest bug.
Thanks for all your help! :)
Comment 18•16 years ago
|
||
Bram, you should also check the latest Shiretoko (1.3) nightly build. Please report back so we can mark this bug verified.
Steven, are you ok with that too?
Status: NEW → RESOLVED
Closed: 16 years ago
Depends on: 467562
Keywords: fixed1.9.1
Resolution: --- → FIXED
Whiteboard: [fixed by bug 467562]
Target Milestone: --- → Firefox 3.2a1
Comment 19•16 years ago
|
||
> Steven, are you ok with that too?
Are you still able to reproduce your problems with older nightlies (made before the patch for bug 467562 was landed)?
Then marking this bug fixed is fine with me (and my STR from comment #10 is presumably unrelated).
Comment 20•16 years ago
|
||
I was wrong. Today morning I've seen the same again in a tab with Gmail open. I had to reload the whole page to be able to access Gmail again.
It looks like that bug 470274 is related to this problem.
Status: RESOLVED → REOPENED
Component: General → Networking
Keywords: fixed1.9.1
Product: Firefox → Core
QA Contact: general → networking
Resolution: FIXED → ---
Whiteboard: [fixed by bug 467562]
Target Milestone: Firefox 3.2a1 → ---
Comment 21•16 years ago
|
||
Can we reproduce this with any website other than GMail? Are we sure that this isn't them leaving an XmlHttpRequest open with some sort of timeout that breaks when we restore from sleep?
Comment 22•16 years ago
|
||
just sort of fyi, 467562 would have impacted DNS where pr_intervals could have wrapped while sleeping: it would take around 35 minutes I believe. That fix should have landed around Jan 14th, and I can't see anyway DNS would be related to the online/offline issues in 470274.. but I'm looking.
Comment 23•14 years ago
|
||
bug 467562 and bug 470274 are fixed long ago.
So can this still be reproduced?
Comment 24•14 years ago
|
||
no response, so => WFM based on comment 17 and comment 20
please reopen if you disagree
Status: REOPENED → RESOLVED
Closed: 16 years ago → 14 years ago
Resolution: --- → WORKSFORME
Whiteboard: [closeme 2011-03-01]
Comment 25•12 years ago
|
||
I think this needs to be reopened. I recently installed OS X 10.8.2 and now firefox consistently hangs on wake up from hibernation for a minute or two.
I do not use gmail with firefox. I'm normally connected to http://prodgame11.lordofultima.com/97/index.aspx and http://louopt.com/ (I have two tabs open).
version 16.0.1: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20100101 Firefox/16.0
Comment 26•12 years ago
|
||
fyi: I'm on a mac laptop and connect wirelessly through DSL.
Comment 27•10 years ago
|
||
Can this be reopened?
This issue is still prevalent in Firefox 35 on Windows 8.1. When waking from hibernation (windows 8.1 with latest updates), all Firefox windows display a blank white block. No chrome, no title, no toolbars, nothing.
The weird thing is Firefox is still running. Menu clicking / tapping on the Firefox icon in the taskbar still allows me to open new windows and load pages in these new windows while the previously open windows (from before the computer hibernated) remain in a blank white oblivion. Right clicking in the blank windows displays the menu shadow. Clicking away hides the shadow which implies that Firefox is still doing something but is unable to render. Not sure how to glean more information to help with this bug.
Comment 28•10 years ago
|
||
(In reply to Jai'prakash from comment #27)
> Can this be reopened?
>
no.. the bug was closed 4 years ago in the core::networking component.. the right thing to do is open a new bug for firefox general - what you describe isn't really a network phenomenon.
thanks!
Comment 29•10 years ago
|
||
I am having the same problem...
Comment 30•10 years ago
|
||
Ramsey, if you can reproduce the problem with Firefox in safe mode, then please open a new bug report. Thanks.
Whiteboard: [see comment 28]
Comment 31•9 years ago
|
||
I have reproduced this with ffx ESR 38.4.0 in Safe Mode on OSX 10.9.5.
Other reports:
https://bugzilla.mozilla.org/show_bug.cgi?id=969266
https://bugzilla.mozilla.org/show_bug.cgi?id=1204282
https://bugzilla.mozilla.org/show_bug.cgi?id=1204297
You need to log in
before you can comment on or make changes to this bug.
Description
•