1054729 - Gfx-corruption in 2014-08-14 onwards (IntelHD in a Optimus-combo)

Status: RESOLVED DUPLICATE of bug 1040187

(Core :: Graphics, defect)

Description

[Elbart]

Attachment: nightly optimus.png

STR:
- Open Nightly
- Middle-click on the "Get your NIghtly User badge"-link

AR: GFX-bugs in the tab bar from the animations

ER: No bugs.

Win7 SP1 x64
Nightly 2014-08-14 onwards
IntelHD/Geforce 310M Optimius

Firefox is run with default settings on the IntelHD-GPU.

HWA off / OMTC on : no bug
HWA off / OMTC off: no bug
HWA on  / OMTC on : bug
HWA on  / OMTC off: crashes right after startup

>==========
[4452] ###!!! ABORT: Reference mD3D9ThebesSurface
 must be released by caller of Begin() before calling End(): file c:\builds\moz2
_slave\m-cen-w32-ntly-000000000000000\build\gfx\layers\d3d9/ThebesLayerD3D9.cpp,
 line 462

(nightly 2014-08-14)
>==========



about:support in 2014-08-16:

>==========
 Application Basics
------------------

Name: Firefox
Version: 34.0a1
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:34.0) Gecko/20100101 Firefox/34.0
Multiprocess Windows: 0/1

Crash Reports for the Last 3 Days
---------------------------------

Report ID: bp-8faf21a1-b1cf-4f17-ba9c-6d33b2140817
Submitted: 1 minute ago

Report ID: bp-5123de6b-3c91-41eb-8439-91c8e2140817
Submitted: 4 minutes ago

Report ID: bp-aa46cbc9-24f2-4aa5-8659-525532140817
Submitted: 29 minutes ago

Report ID: bp-af190e80-9df9-47f6-b67e-3c6622140817
Submitted: 30 minutes ago

Graphics
--------

Adapter Description: Intel(R) HD Graphics
Adapter Description (GPU #2): NVIDIA GeForce 310M
Adapter Drivers: igdumd64 igd10umd64 igdumdx32 igd10umd32
Adapter Drivers (GPU #2): nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um
Adapter RAM: Unknown
Adapter RAM (GPU #2): 1024
ClearType Parameters: Gamma: 2200 Pixel Structure: R ClearType Level: 100 Enhanced Contrast: 50
Device ID: 0x0046
Device ID (GPU #2): 0x0a70
Direct2D Enabled: Blocked for your graphics card because of unresolved driver issues.
DirectWrite Enabled: false (6.2.9200.16571)
Driver Date: 1-30-2013
Driver Date (GPU #2): 7-2-2014
Driver Version: 8.15.10.2993
Driver Version (GPU #2): 9.18.13.4052
GPU #2 Active: false
GPU Accelerated Windows: 1/1 Direct3D 11 (OMTC)
Subsys ID: 12d21043
Subsys ID (GPU #2): 12d21043
Vendor ID: 0x8086
Vendor ID (GPU #2): 0x10de
WebGL Renderer: Google Inc. -- ANGLE (Intel(R) HD Graphics Direct3D9Ex vs_3_0 ps_3_0)
windowLayerManagerRemote: true
AzureCanvasBackend: skia
AzureContentBackend: cairo
AzureFallbackCanvasBackend: cairo
AzureSkiaAccelerated: 0

Important Modified Preferences
------------------------------

gfx.direct3d.last_used_feature_level_idx: 1
>==========

The crashreports mentioned there are from hwa on/omtc off.


Regression-range:

Last good revision: 7fc96293ada8 (2014-08-13)
First bad revision: 5299864050ee (2014-08-14)
Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=7fc96293ada8&tochange=5299864050ee

Last good revision: 81c93f4a6212
First bad revision: 043edc92814e
Pushlog:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=81c93f4a6212&tochange=043edc92814e

Maybe
9c339e14c720	David Parks — Bug 1008759 - Blocklist D2D on NVidia 310M, even when it is believed to be the secondary GPU. r=bjacob

Comment 1

[Elbart]

This is happening in both a normal and in a e10s-window.

Comment 2

[(mostly gone) XtC4UaLL [:xtc4uall]]

Thanks for filling this. I literally was just about to do this myself right now.

This also affects content like when scrolling on Twitter's timeline.
Seems like a layers invalidation issue.

Comment 3

[(mostly gone) XtC4UaLL [:xtc4uall]]

Attachment: content corruption

Comment 4

[(mostly gone) XtC4UaLL [:xtc4uall]]

Disabling D3D via layers.acceleration.disabled;true helps.

Comment 5

[(mostly gone) XtC4UaLL [:xtc4uall]]

with gfx.direct2d.disabled;true I get:

Last good revision: 196d05832e12 (2014-07-09)
First bad revision: cb75d6cfb004 (2014-07-10)
Pushlog: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=196d05832e12&tochange=cb75d6cfb004

Last good revision: b37955bdf1b6
First bad revision: 99690880e8f5
Pushlog: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=b37955bdf1b6&tochange=99690880e8f5

=> regressed by Bug 1035227
=> dupe of Bug 1040187

Comment 6

[Elbart]

Does this mean the IntelHD-gpu is now completely blocked from HWA, too? 
Blocking the 310M doesn't matter, because it wasn't used for Firefox by default.
But having the IntelHD blocked too, that's a low blow.

Comment 7

[(mostly gone) XtC4UaLL [:xtc4uall]]

Well, as you can read in bug 1008759 dual GPU blocklisting is kind of broken, but about to get improved sometime later on. as of now it's blocking both or nothing.

As a workaround until e10s is default on you can force enable D2D.