Closed Bug 304298 Opened 19 years ago Closed 17 years ago

Firefox doesn't open any www-page after Macosx has gone into "Sleep" state

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Version:
1.0 Branch
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: saku.jokinen, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

When mac is gone to "sleep" state and Firefox browser window is kept open,
Firefox can open any page after system is being woke up again. In other words
Firefox needs to be restarted after mac being in sleep status.

Reproducible: Always

Steps to Reproduce:
1. Open Firefox
2. Put mac into sleep 
3. try to open any page
This reminds me of bug 232715, but that was fixed for FF 1.0.x.
This remainds lot bug mentioned in previous comment. I have some further information regarding this. If 
you hit reload button after waking computer from sleep state, everything seems to work as per normal. 
However, if you try to open other pages by writing new URL to URL field, most probaply page won't open. 
I'm using MacOSX 10.4.2
I tried many different things, but I cannot recreate.  Tried with FF 1.0.6, Deer
Park a2, and a branch nightly, and never saw what you are seeing.  Have you
tried with a branch nightly?
this is likley the same as #232715 and #325188 but is hard to verify as the bug (esp. #325188) doesnt present every time machine is swithced into sleep mode or even when hard drive sleeps. have repeatedly tried to get firefox to replicate this bhaviour, but works perfectly after sleeping (this not was written on a new page after machine was woken from sleep!).
Oh god, I hope this isn't back again ;) A few things to consider:

1. do you have any third party browser extensions or browser themes installed?

2. does it do this regardless of what pages you visited prior to the computer going to sleep? I know Darren's already indicated that it doesn't do it all the time, so maybe it depends on the type of pages that were loaded prior to sleep. For example, maybe only after Java has been loaded, or Flash?

3. does it break if you force the computer to sleep (selecting Sleep from the Apple menu), or only when the timed system sleep comes on? The latter was the case for bug 232715, and could explain why it's reproducible some times, and not others.

4. What version(s) of OS X has this been reproduced on?
(In reply to comment #5)
> Oh god, I hope this isn't back again ;
afraid so my freinds.
 
> 1. do you have any third party browser extensions or browser themes installed?
Default Theme with the following extensions installed:
DOM Inspector 1.8
Talkback 1.5
Adblock 0.5.2.039
PDF Download 0.5.1.2
Fasterfox 1.0.3
WebDeveloper 0.9.4
TickerFox 0.2.6
ChatZilla 0.9.69.1

> 2. does it do this regardless of what pages you visited prior to the computer
> going to sleep?
Yep pretty much, had pages with no flash or java running (doing dev work on CSS and HTML)

> 3. does it break if you force the computer to sleep (selecting Sleep from the
> Apple menu), or only when the timed system sleep comes on?
My machine 'screensaves' when idel and discs stop when not in use (different settings controlling each). Always force sleep when away from machine by touch of power button (same as apple system menu i believe). However, cant reproduce on command by either method.

> 4. What version(s) of OS X has this been reproduced on?
Machine running OSX 10.2.6
Firefox 1.5.0.1 rc1

Hope this of some use to someone :-)
I'll try to test this out on my own machine as soon as I can. In the meantime, one thing I can suggest you try is disabling all your third party extensions and seeing if you can still reproduce the bug.

The first time this happened, to reproduce you had to not only wait till the computer went to sleep (by timing), but also wait for the hard disk to spin down. This took another minute or so after sleep was initiated.
still unable to reproduce, as stated previously seems to be intermitant, more often working than not. dont you just hate it when that happens... you know theres a problem and you know approximatly its trigger or location, but somehow it evades you.
I can't reproduce on my home machine: PowerMac G4, OS X 10.4.4, latest Deer Park trunk nightly.

But my set up has changed a bit since the days of bug 232715. I no longer use my computer's modem, which may have been part of the issue.

We still need a test case that's reproducible. Lack of consistency means it's not 100% identical to bug 232715. Hopefully you guys who see the bug sometimes can work out the right conditions. I'm still suspicious of all those extensions...
OK, finally seeing a sleep-related bug. Afterwards, I can't even switch between tabs, or quit the browser, and have to force quit. But only after long sleep, and I haven't found a 100% reproducible method yet. Trying to find one...
See Bug 327050/Bug 213637.
I'm experiencing this bug in Windows Vista (not running on a Mac).  Hmmm, I believe recent MacBooks and my lappy share the same wireless chipset.  It did not occur under XP on the same system.  I have noticed the same thing as Wayne, that it usually happens after a long sleep.  I can't just put the machine to sleep, bring it back, and experience the bug.

Has anyone tried accessing a non-HTTP website when this bug occurs?  How about localhost?  I will do so next time and report back.
This worksforme in Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.9a7pre) Gecko/2007072204 Minefield/3.0a7pre

This is on an Intel iMac 2.16Ghz. Can anyone confirm whether or not they are still seeing this bug on a more recent build of Firefox?
Upgraded the OS a few weeks ago, now running Mac OS 10.4.10.

The version of firefox im using at the moment reports as:
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6

and No i havent seen this bug for a long time.

I dont know if it has been 'fixed' as such, i suspect its either idle again, or its been coded out as a consequence of other changes. If anyone else has experienced this bug more recently please comment, otherwise this bug report is likely to be closed.
W.Woods also says "it's been so long I don't think it exists anymore.", so => WFM
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
Version: unspecified → 1.0 Branch
You need to log in before you can comment on or make changes to this bug.