Closed Bug 1052511 Opened 11 years ago Closed 4 years ago

Hang during display driver crash and recover after laptop startup [@ LockD3DTexture][@ TextureClientD3D11::Lock]

Categories

(Core :: Graphics: Layers, defect)

x86_64
Windows 8.1
defect
Not set
critical

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: cmtalbert, Unassigned)

References

()

Details

(Keywords: hang)

This is very similar to bug 1016028, but in a different place, so I filed a different bug, feel free to dupe. I started up the laptop this morning, connected to an external display and at first the display didn't start up (i.e. black) then it flickered, and then it came up. Windows informed me that there had been a display driver crash and restore. I was running nightly and it now took up full screen (it was probably full screen when I closed the laptop last night) and was entirely white. Nothing was rendered except the top gray bar containing the icon, the page title it had been on (zimbra) and the standard windows 3 button window controls. I attached to it in the debugger and got the stack below. In particular, it looks like we attempt to acquire the texture lock and wait forever, and since this crash destroyed the state of the display driver, we are going to wait forever and never recover. I don't know what we can do here or how common this is - first time I've seen it. Grabbed a dump too: http://people.mozilla.org/~ctalbert/dumps/firefox.dmp.gz Stack: xul.dll!mozilla::layers::LockD3DTexture<ID3D10Texture2D>(ID3D10Texture2D * aTexture) Line 112 xul.dll!mozilla::layers::TextureClientD3D11::Lock(mozilla::layers::OpenMode aMode) Line 210 xul.dll!mozilla::layers::ContentClientDoubleBuffered::FinalizeFrame(const nsIntRegion &aRegionToDraw) Line 548 xul.dll!mozilla::layers::RotatedContentBuffer::BeginPaint(mozilla::layers::ThebesLayer * aLayer, unsigned int aFlags) Line 535 xul.dll!mozilla::layers::ContentClientRemoteBuffer::BeginPaintBuffer(mozilla::layers::ThebesLayer * aLayer, unsigned int aFlags) Line 214 xul.dll!mozilla::layers::ClientThebesLayer::PaintThebes() Line 56 xul.dll!mozilla::layers::ClientThebesLayer::RenderLayerWithReadback(mozilla::layers::ReadbackProcessor * aReadback) Line 133 xul.dll!mozilla::layers::ClientContainerLayer::RenderLayer() Line 72 xul.dll!mozilla::layers::ClientLayer::RenderLayerWithReadback(mozilla::layers::ReadbackProcessor * aReadback) Line 337 xul.dll!mozilla::layers::ClientContainerLayer::RenderLayer() Line 72 xul.dll!mozilla::layers::ClientLayerManager::EndTransactionInternal(void (mozilla::layers::ThebesLayer *, gfxContext *, const nsIntRegion &, mozilla::layers::DrawRegionClip, const nsIntRegion &, void *) * aCallback, void * aCallbackData, mozilla::layers::LayerManager::EndTransactionFlags __formal) Line 221 xul.dll!mozilla::layers::ClientLayerManager::EndTransaction(void (mozilla::layers::ThebesLayer *, gfxContext *, const nsIntRegion &, mozilla::layers::DrawRegionClip, const nsIntRegion &, void *) * aCallback, void * aCallbackData, mozilla::layers::LayerManager::EndTransactionFlags aFlags) Line 247 xul.dll!nsDisplayList::PaintForFrame(nsDisplayListBuilder * aBuilder, nsRenderingContext * aCtx, nsIFrame * aForFrame, unsigned int aFlags) Line 1344 xul.dll!nsLayoutUtils::PaintFrame(nsRenderingContext * aRenderingContext, nsIFrame * aFrame, const nsRegion & aDirtyRegion, unsigned int aBackstop, unsigned int aFlags) Line 3064 xul.dll!PresShell::Paint(nsView * aViewToPaint, const nsRegion & aDirtyRegion, unsigned int aFlags) Line 6239 xul.dll!nsViewManager::ProcessPendingUpdatesPaint(nsIWidget * aWidget) Line 443 xul.dll!nsViewManager::ProcessPendingUpdatesForView(nsView * aView, bool aFlushDirtyRegion) Line 380 xul.dll!nsRefreshDriver::Tick(__int64 aNowEpoch, mozilla::TimeStamp aNowTime) Line 1284
Forgot to mention (sorry): Yesterday's (August 11 nightly). Laptop: lenovo x240 Intel HD4400 Graphics GPU, running windows 8.1
cmtalbert, still see these hangs?
Severity: normal → critical
Flags: needinfo?(cmtalbert)
Keywords: hang
See Also: → 1016028

Marking this as Resolved > Incomplete as the reporter cannot be contacted for a confirmation of the issue.
If anyone can still repro the issue please re-open it or file a new bug.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
Flags: needinfo?(cmtalbert)
You need to log in before you can comment on or make changes to this bug.