627154 - Docking or undocking causes FF to stop painting although it keeps executing

Status: RESOLVED DUPLICATE of bug 626678

(Core :: Graphics, defect)

Description

[Allison Naaktgeboren :ally]

User-Agent:       Mozilla/5.0 (Windows NT 5.1; rv:2.0b9) Gecko/20100101 Firefox/4.0b9
Build Identifier: 4.0b9 -- http://hg.mozilla.org/mozilla-central/rev/859a97109032 

When laptop is undocked or docked, FF, the error console, the download manager, etc if open stop painting. 

WM_PAINTs arrive, mouse clicks, focus, max, min, etc.  FF appears to continue to function (can navigate to new tabs, or change url in current, menus are still generated and entries can be activated,etc)/  Video drivers do not report any crashes or malfunction, there is no spike in cpu or memory consumption.  

Reproducible: Always

Steps to Reproduce:
1.open FF
2.undock
3.poke FF (where poke is defined as 'ctrl+T, click into where url bar should be, go to www.pandora.com, hear music')
Actual Results:  
FF doesnt repaint itself


machine is a dell. I dont own any other machine with a dock and the rest of the office uses chrome.

Comment 1

[Bas Schouten (:bas.schouten)]

Could you post the graphics section from about:support? And also try with the latest nightly please!

Comment 2

[Allison Naaktgeboren :ally]

Bas,
Graphics
Adapter Description NVIDIA NVS 3100M
Vendor ID10de
Device ID0a6c
Adapter RAMUnknown
Adapter Driversnv4_dispDriver 
Version6.14.11.8921
Driver Date2-19-2010
Direct2D Enabledfalse
DirectWrite Enabledfalse
WebGL RendererNVIDIA Corporation -- NVS 3100M/PCI/SSE2 -- 3.1 NVIDIA 189.21
GPU Accelerated Windows1/1 Direct3D 9

Comment 3

[Allison Naaktgeboren :ally]

Happens on the version I just pulled from http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/ .

Comment 4

[Allison Naaktgeboren :ally]

Bas, I installed 4.0b11pre today.  The issue still expresses. However, if I disable the hardware acceleration, the bug does not express.  

from about:support
GPU Accelerated Windows0/1

Comment 5

[(mostly gone) XtC4UaLL [:xtc4uall]]

Dupe/related to Bug 626678?