Created attachment 8558786 [details] firefox-bug.jpg User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0 Build ID: 20150122214805 Steps to reproduce: In several sites noticed the problem, sometimes in some places appear black boxes (or something similar). I believe it is a problem related to the "DirectX". - In https://docs.google.com/spreadsheets/ move mouse on "title colum" for reproduce problem). - In <textarea> with great content (in example I used stackexchange community, but the problem occurs in any textarea)
Can you please open about:support (enter as url) copy the Graphic section and post it here as comment ?
Graphics: Adapter Description: Intel(R) HD Graphics Adapter Drivers: igdumd64 igd10umd64 igdumdx32 igd10umd32 Adapter RAM: Unknown ClearType Parameters: Gamma: 2200 Pixel Structure: R ClearType Level: 100 Enhanced Contrast: 50 Device ID: 0x0046 Direct2D Enabled: Blocked for your graphics driver version. Try updating your graphics driver to version 8.1500.1000.2202 or newer. DirectWrite Enabled: false (6.1.7600.21162) Driver Date: 24.04.2011 Driver Version: 188.8.131.529 GPU #2 Active: false GPU Accelerated Windows: 1/1 Direct3D 11 (OMTC) Subsys ID: 144c103c Vendor ID: 0x8086 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
Looks like D3D11 OMTC hitting driver bug. Bas do we have something riding the trains to address this? Should we make this old driver version hit D3D9 instead?
(In reply to Benoit Girard (:BenWa) from comment #3) > Looks like D3D11 OMTC hitting driver bug. Bas do we have something riding > the trains to address this? Should we make this old driver version hit D3D9 > instead? It's hard to say for sure but it's at least fairly unlikely to be a driver bug I think.
(In reply to Benoit Girard (:BenWa) from comment #3) > Looks like D3D11 OMTC hitting driver bug. Bas do we have something riding > the trains to address this? Should we make this old driver version hit D3D9 > instead? (FWIW they'd be moved to D3D11-WARP and not D3D9)
Is this still around after bug 1148855 landed?
Guilherme, can you please check the latest Beta from https://beta.mozilla.org/ and see if this still reproduces for you?