458165 - White screen of death after waking from sleep

Status: RESOLVED INVALID

(Firefox :: Session Restore, defect)

Description

[roarkh]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3

When I put my desktop to sleep and wake it up, after 2 or more sessions of this, clicking on a Firefox window (usually with some type of webmail) causes the whole screen to blank to white.  Unable to leave white screen with either (alt-tab, alt-f4, or ctl-alt-del).  

Only started happening recently (after 5.02 patch).

Desktop is using an Nvidia card (8800gtx) latest drivers and windows vista 64 home premium (8gb of physical mem, no paging file).  Quadcore 2.53Ghz.

Problem was also reported on UMPCPortal.com as happening with a Gigabyte M912 netbook w/ Firefox.. no details though.

Reproducible: Always

Steps to Reproduce:
1. Open 2-3 firefox windows (with at least 1-3 tabs each)
2. Put machine to sleep, wake after several minutes or an hour.
3. Click on firefox window to make it frontmost..  
4. Repeat steps 2-3 several times (usually occurs after 2 wakes).
Actual Results:  
whole screen turns white.  no way to leave.

Requires Power button 30sec hold down or power switch reset.
(interesting enough, hdd looks like it's still working).

Expected Results:  
Give me a break, not white out the screen.. how about show the window properly

Detail config:

QuadCore 2.53Ghz, Intel
8GB of Memory
Gigabyte Mobo, latest BIOS (G33 series)
dual 750GB HDD (Western Digital)
Vista Home Premium 64Bit (latest patches.. as of Sept 29).
Nvidia (leadtek) 8800GTX w/ 512Meg Memory
  Latest Nvidia drivers.
Dell 24" 1920x1200 Monitor
Keyboard, Video, Mouse through an iogear DVI KVM.

Comment 1

[Matthias Versen [:Matti]]

Firefox doesn't come with any device drivers that are running with kernel mode and that means that the OS must be always be able to kill Firefox which is a user space application.
It could take a few seconds for the taskmanager to come up in the worst case if Firefox would allocate all available RAM but it should be killable.
If you can not kill Firefox then this is a clear system or driver bug but not Firefox fault. It's possible that you get this issue only with Firefox but that doesn't mean that it's a Firefox bug.

marking invalid

Comment 2

[roarkh]

Interesting comment as firefox is a tcp/ip application and unless microsoft changed something (which I doubt), still has a blocking semaphore on the stack.  A network application (any even in application space only) can 'lock up/hang' a system waiting for a missed response.  A bad screen redraw and this situation (especially after a wakeup, which could cause a network application to hang as the stack would not be available yet.. i.e; pulled from under firefox on sleep) can cause this occurance.  I do not believe I waited long enough to see if Vista would find it unresponsive and kill it.. but again depending on the state, it might not be immediately killable.

Comment 3

[Ria Klaassen (not reading all bugmail)]

I believe a similar hang after wake-up was reported shortly before. Are you sure the hang is not caused by an old plugin?