1234616 - MS SurfaceBook - Frequent painting / invalidation problems in chrome ui.

Status: NEW

(Core :: Graphics, defect, P3)

Description

[Doug Turner (:dougt)]

Frequently I see the chrome UI not painted correctly and/or context menus painted all black.  Not sure how to repro.

I'll attach screen shots next time it happens...




Application Basics
------------------

Name: Firefox
Version: 43.0.1
Build ID: 20151216175450
Update Channel: release
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0
Multiprocess Windows: 0/1 (default: false)
Safe Mode: false

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

All Crash Reports

Extensions
----------

Name: 1Password
Version: 4.5.1
Enabled: true
ID: [e-mail]

Name: Adblock Plus
Version: 2.7
Enabled: true
ID: {d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}

Graphics
--------

Adapter Description: Intel(R) HD Graphics 520
Adapter Description (GPU #2): NVIDIA GeForce GPU
Adapter Drivers: igdumdim64 igd10iumd64 igd10iumd64 igd12umd64 igdumdim32 igd10iumd32 igd10iumd32 igd12umd32
Adapter Drivers (GPU #2): nvd3dumx,nvwgf2umx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um,nvwgf2um
Adapter RAM: Unknown
Adapter RAM (GPU #2): 1024
Asynchronous Pan/Zoom: none
Device ID: 0x1916
Device ID (GPU #2): 0x134b
Direct2D Enabled: true
DirectWrite Enabled: true (10.0.10586.0)
Driver Date: 11-20-2015
Driver Date (GPU #2): 9-15-2015
Driver Version: 20.19.15.4326
Driver Version (GPU #2): 10.18.13.5415
GPU #2 Active: false
GPU Accelerated Windows: 1/1 Direct3D 11 (OMTC)
Subsys ID: 00141414
Subsys ID (GPU #2): 00081414
Supports Hardware H264 Decoding: Yes
Vendor ID: 0x8086
Vendor ID (GPU #2): 0x10de
WebGL Renderer: Google Inc. -- ANGLE (Intel(R) HD Graphics 520 Direct3D11 vs_5_0 ps_5_0)
windowLayerManagerRemote: true
AzureCanvasBackend: direct2d 1.1
AzureContentBackend: direct2d 1.1
AzureFallbackCanvasBackend: cairo
AzureSkiaAccelerated: 0
(#0) Error: [D2D1.1] 4CreateBitmap failure Size(32,24914) Code: 0x80070057 format 0
(#1) Error: [D2D1.1] 4CreateBitmap failure Size(32,24914) Code: 0x80070057 format 0

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

accessibility.typeaheadfind.flashBar: 0
browser.cache.disk.capacity: 358400
browser.cache.disk.filesystem_reported: 1
browser.cache.disk.smart_size.first_run: false
browser.cache.frecency_experiment: 2
browser.download.importedFromSqlite: true
browser.download.manager.alertOnEXEOpen: true
browser.places.smartBookmarksVersion: 7
browser.sessionstore.upgradeBackup.latestBuildID: 20151216175450
browser.startup.homepage_override.buildID: 20151216175450
browser.startup.homepage_override.mstone: 43.0.1
dom.apps.reset-permissions: true
dom.mozApps.used: true
extensions.lastAppVersion: 43.0.1
gfx.crash-guard.d3d11layers.appVersion: 43.0.1
gfx.crash-guard.d3d11layers.deviceID: 0x1916
gfx.crash-guard.d3d11layers.driverVersion: 20.19.15.4326
gfx.crash-guard.d3d11layers.feature-d2d: true
gfx.crash-guard.d3d11layers.feature-d3d11: true
gfx.crash-guard.glcontext.gfx.driver-init.direct3d11-angle: true
gfx.crash-guard.glcontext.gfx.driver-init.webgl-angle: true
gfx.crash-guard.glcontext.gfx.driver-init.webgl-angle-force-d3d11: false
gfx.crash-guard.glcontext.gfx.driver-init.webgl-angle-force-warp: false
gfx.crash-guard.glcontext.gfx.driver-init.webgl-angle-try-d3d11: true
gfx.crash-guard.status.d3d11layers: 2
gfx.crash-guard.status.d3d9video: 2
gfx.crash-guard.status.glcontext: 2
gfx.direct3d.last_used_feature_level_idx: 0
gfx.driver-init.appVersion: 42.0
gfx.driver-init.deviceID: 0x1916
gfx.driver-init.driverVersion: 20.19.15.4326
gfx.driver-init.feature-d2d: true
gfx.driver-init.feature-d3d11: true
gfx.driver-init.status: 2
media.gmp-eme-adobe.abi: x86-msvc
media.gmp-eme-adobe.lastUpdate: 1449780928
media.gmp-eme-adobe.version: 15
media.gmp-gmpopenh264.abi: x86-msvc
media.gmp-gmpopenh264.lastUpdate: 1449780930
media.gmp-gmpopenh264.version: 1.5.1
media.gmp-manager.buildID: 20151216175450
media.gmp-manager.lastCheck: 1450741642
media.hardware-video-decoding.failed: false
network.cookie.prefsMigrated: true
network.predictor.cleaned-up: true
places.database.lastMaintenance: 1450419803
places.history.expiration.transient_current_max_pages: 104858
plugin.disable_full_page_plugin_for_types: application/pdf
plugin.importedState: true
print.printer_Microsoft_Print_to_PDF.print_bgcolor: false
print.printer_Microsoft_Print_to_PDF.print_bgimages: false
print.printer_Microsoft_Print_to_PDF.print_duplex: -437918235
print.printer_Microsoft_Print_to_PDF.print_edge_bottom: 0
print.printer_Microsoft_Print_to_PDF.print_edge_left: 0
print.printer_Microsoft_Print_to_PDF.print_edge_right: 0
print.printer_Microsoft_Print_to_PDF.print_edge_top: 0
print.printer_Microsoft_Print_to_PDF.print_evenpages: true
print.printer_Microsoft_Print_to_PDF.print_footercenter:
print.printer_Microsoft_Print_to_PDF.print_footerleft: &PT
print.printer_Microsoft_Print_to_PDF.print_footerright: &D
print.printer_Microsoft_Print_to_PDF.print_headercenter:
print.printer_Microsoft_Print_to_PDF.print_headerleft: &T
print.printer_Microsoft_Print_to_PDF.print_headerright: &U
print.printer_Microsoft_Print_to_PDF.print_in_color: true
print.printer_Microsoft_Print_to_PDF.print_margin_bottom: 0.5
print.printer_Microsoft_Print_to_PDF.print_margin_left: 0.5
print.printer_Microsoft_Print_to_PDF.print_margin_right: 0.5
print.printer_Microsoft_Print_to_PDF.print_margin_top: 0.5
print.printer_Microsoft_Print_to_PDF.print_oddpages: true
print.printer_Microsoft_Print_to_PDF.print_orientation: 0
print.printer_Microsoft_Print_to_PDF.print_page_delay: 50
print.printer_Microsoft_Print_to_PDF.print_paper_data: 1
print.printer_Microsoft_Print_to_PDF.print_paper_height: 11.00
print.printer_Microsoft_Print_to_PDF.print_paper_name:
print.printer_Microsoft_Print_to_PDF.print_paper_size_type: 0
print.printer_Microsoft_Print_to_PDF.print_paper_size_unit: 0
print.printer_Microsoft_Print_to_PDF.print_paper_width: 8.50
print.printer_Microsoft_Print_to_PDF.print_resolution: -437918235
print.printer_Microsoft_Print_to_PDF.print_reversed: false
print.printer_Microsoft_Print_to_PDF.print_scaling: 1.00
print.printer_Microsoft_Print_to_PDF.print_shrink_to_fit: true
print.printer_Microsoft_Print_to_PDF.print_to_file: false
print.printer_Microsoft_Print_to_PDF.print_unwriteable_margin_bottom: 0
print.printer_Microsoft_Print_to_PDF.print_unwriteable_margin_left: 0
print.printer_Microsoft_Print_to_PDF.print_unwriteable_margin_right: 0
print.printer_Microsoft_Print_to_PDF.print_unwriteable_margin_top: 0
privacy.sanitize.migrateFx3Prefs: true
storage.vacuum.last.index: 1
storage.vacuum.last.places.sqlite: 1449781490
ui.osk.debug.keyboardDisplayReason: IKPOS: ConvertibleSlateMode is non-zero

Important Locked Preferences
----------------------------

JavaScript
----------

Incremental GC: true

Accessibility
-------------

Activated: true
Prevent Accessibility: 0

Library Versions
----------------

NSPR
Expected minimum version: 4.10.10
Version in use: 4.10.10

NSS
Expected minimum version: 3.20.1 Basic ECC
Version in use: 3.20.1 Basic ECC

NSSSMIME
Expected minimum version: 3.20.1 Basic ECC
Version in use: 3.20.1 Basic ECC

NSSSSL
Expected minimum version: 3.20.1 Basic ECC
Version in use: 3.20.1 Basic ECC

NSSUTIL
Expected minimum version: 3.20.1
Version in use: 3.20.1

Experimental Features
---------------------

Comment 1

[Milan Sreckovic [:milan] (needinfo for best results)]

Could start with an assumption that it's related to the error messages.  OptimizeSourceSurface and GetDataSurface don't always seem to succeed, but not all the callers appear ready for it.  In particular, SourceSurfaceCairo::GetDataSurface doesn't seem to be checking if the cairo call succeeded?

Comment 2

[Milan Sreckovic [:milan] (needinfo for best results)]

Bas, why are we attempting to make a D2D texture with a dimension of 24914?  Don't we have something in place that stops us before we get that deep into accelerated code path?

Comment 3

[Bas Schouten (:bas.schouten)]

(In reply to Milan Sreckovic [:milan] from comment #2)
> Bas, why are we attempting to make a D2D texture with a dimension of 24914? 
> Don't we have something in place that stops us before we get that deep into
> accelerated code path?

What should happen in this codepath (and from what I can tell would happen), is the D2D error will just cause us to 'not optimize' the DataSourceSurface. We should then attempt to draw directly with the DataSourceSurface and it -shouldn't- cause any problems. It's hard to say whether the error is actually related to the problem, DougT was going to put a breakpoint on the error to see where it's coming from.

Most likely I suspect the drawing issues and this error may have a -common cause- rather than being directly causally related. If they're related at all. I wonder if Doug ever managed to get the stack trace.

Comment 4

[Doug Turner (:dougt)]

Nothing under the debugger yet.

Comment 5

[Doug Turner (:dougt)]

fwiw, i have not seen this in nightly.

Comment 6

[Bas Schouten (:bas.schouten)]

(In reply to Doug Turner (:dougt) from comment #5)
> fwiw, i have not seen this in nightly.

I wonder if this was somehow related to partial presents.. maybe those will get disabled now on the SurfaceBook.

Comment 7

[Milan Sreckovic [:milan] (needinfo for best results)]

We have seen a number of these problems traced down to driver issues.

Comment 8

[Doug Turner (:dougt)]

milan, other browsers don't seem to have this problem. Can't we work around driver issues?

Comment 9

[Milan Sreckovic [:milan] (needinfo for best results)]

(In reply to Doug Turner (:dougt) from comment #8)
> milan, other browsers don't seem to have this problem. Can't we work around
> driver issues?

Right - based on some information from AMD (they were of huge help here), we have reasons to believe it's the higher than usual number of D3D devices in Firefox (we use one per video, and the usual total is 1) that's hitting a race condition (which AMD has fixed in their latest driver.)  We don't have direct evidence that we're hitting the same problem with other vendors, but the problems look reasonably similar, so the current theory is that it is the same issue. 

Bug 1284672 is where we're trying to reduce the number of devices used.

Comment 10

[u279076]

It's been a couple months since AMD's driver was updated and it looks like bug 1284672 has been fixed since then. Can we get this retested to see if the situation is resolved or at least improved?