Closed
Bug 1014378
Opened 10 years ago
Closed 3 years ago
Firefox window is not rendered after OMTC enabled
Categories
(Core :: Graphics, defect)
Core
Graphics
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: JasnaPaka, Assigned: bas.schouten)
References
Details
Attachments
(1 file)
125.20 KB,
image/png
|
Details |
Firefox Nightly, latest build. After OTMC enabled on Windows Firefox window is not rendered correctly (see screenshot). Windows 7, HWA enabled. Not sure what I can provide for debugging (just say). about:support ============== drivers: igdumd64 igd10umd64 igd10umd64 igdumdx32 igd10umd32 igd10umd32 description: Intel(R) HD Graphics Family version: 8.15.10.2347
Comment 1•10 years ago
|
||
Turning OMTC off in the prefs fixes the problem?
Blocks: 899785
Summary: Firefox window is not rendered after OTMC enabled → Firefox window is not rendered after OMTC enabled
Reporter | ||
Comment 2•10 years ago
|
||
Yes, layers.offmainthreadcomposition.enabled to false fixed my problem.
Assignee | ||
Comment 3•10 years ago
|
||
This is very interesting, could you paste you full about:support graphics section when OMTC is disabled?
Assignee: nobody → bas
Status: NEW → ASSIGNED
Reporter | ||
Comment 4•10 years ago
|
||
Full graphics section from about:support: Adapter Description Intel(R) HD Graphics Family Adapter Drivers igdumd64 igd10umd64 igd10umd64 igdumdx32 igd10umd32 igd10umd32 Adapter RAM Unknown Device ID 0x0126 Direct2D Enabled true DirectWrite Enabled true (6.2.9200.16571) Driver Date 3-28-2011 Driver Version 8.15.10.2347 GPU #2 Active false GPU Accelerated Windows 1/1 Direct3D 10 Vendor ID 0x8086 WebGL Renderer Google Inc. -- ANGLE (Intel(R) HD Graphics Family Direct3D9Ex vs_3_0 ps_3_0) windowLayerManagerRemote false AzureCanvasBackend direct2d AzureContentBackend direct2d AzureFallbackCanvasBackend cairo AzureSkiaAccelerated 0
Assignee | ||
Comment 5•10 years ago
|
||
(In reply to Pavel Cvrcek (Mozilla.cz) [:JasnaPaka] from comment #4) > Full graphics section from about:support: > > Adapter Description Intel(R) HD Graphics Family > Adapter Drivers igdumd64 igd10umd64 igd10umd64 igdumdx32 igd10umd32 > igd10umd32 > Adapter RAM Unknown > Device ID 0x0126 > Direct2D Enabled true > DirectWrite Enabled true (6.2.9200.16571) > Driver Date 3-28-2011 > Driver Version 8.15.10.2347 > GPU #2 Active false > GPU Accelerated Windows 1/1 Direct3D 10 > Vendor ID 0x8086 > WebGL Renderer Google Inc. -- ANGLE (Intel(R) HD Graphics Family Direct3D9Ex > vs_3_0 ps_3_0) > windowLayerManagerRemote false > AzureCanvasBackend direct2d > AzureContentBackend direct2d > AzureFallbackCanvasBackend cairo > AzureSkiaAccelerated 0 Hmmm... could you see what happens if you enable OMTC, but also switch gfx.direct2d.disabled to true?
Reporter | ||
Comment 6•10 years ago
|
||
(In reply to Bas Schouten (:bas.schouten) from comment #5) > Hmmm... could you see what happens if you enable OMTC, but also switch > gfx.direct2d.disabled to true? It works.
Assignee | ||
Comment 7•10 years ago
|
||
(In reply to Pavel Cvrcek (Mozilla.cz) [:JasnaPaka] from comment #6) > (In reply to Bas Schouten (:bas.schouten) from comment #5) > > Hmmm... could you see what happens if you enable OMTC, but also switch > > gfx.direct2d.disabled to true? > > It works. Could you try updating your Intel driver?
Reporter | ||
Comment 8•10 years ago
|
||
(In reply to Bas Schouten (:bas.schouten) from comment #7) > Could you try updating your Intel driver? Yes, after driver update it works fine. Maybe we should blocklist old version of this driver for HWA? Current about:support: Adapter Description Intel(R) HD Graphics 3000 Adapter Drivers igdumd64 igd10umd64 igd10umd64 igdumd32 igd10umd32 igd10umd32 Adapter RAM Unknown Device ID 0x0126 Direct2D Enabled true DirectWrite Enabled true (6.2.9200.16571) Driver Date 1-29-2014 Driver Version 9.17.10.3347 GPU #2 Active false GPU Accelerated Windows 1/1 Direct3D 10 Vendor ID 0x8086 WebGL Renderer Google Inc. -- ANGLE (Intel(R) HD Graphics 3000 Direct3D9Ex vs_3_0 ps_3_0) windowLayerManagerRemote false AzureCanvasBackend direct2d AzureContentBackend direct2d AzureFallbackCanvasBackend cairo AzureSkiaAccelerated 0
Please define what you mean with "old". This is my setup: Application Basics ------------------ Name: Firefox Version: 32.0a1 User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:32.0) Gecko/20100101 Firefox/32.0 ---------- 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: true DirectWrite Enabled: true (6.2.9200.16571) Driver Date: 1-30-2013 Driver Version: 8.15.10.2993 GPU Accelerated Windows: 1/1 Direct3D 10 Vendor ID: 0x8086 WebGL Renderer: Google Inc. -- ANGLE (Intel(R) HD Graphics Direct3D9Ex vs_3_0 ps_3_0) windowLayerManagerRemote: false AzureCanvasBackend: direct2d AzureContentBackend: direct2d AzureFallbackCanvasBackend: cairo AzureSkiaAccelerated: 0 Important Modified Preferences ------------------------------ gfx.direct3d.last_used_feature_level_idx: 1 And I currently have no issues with OMTC. But there are also no newer drivers for this GPU. According to https://wiki.mozilla.org/Blocklisting/Blocked_Graphics_Drivers#Intel_cards, 8.15.10.2302 and newer are required. So raising that limit to .2347 should be enough, no?
Reporter | ||
Comment 10•10 years ago
|
||
Sorry, I don't know. I am not expert in this area.
Comment 12•10 years ago
|
||
I had a play with this, but unfortunately I can't find a way to install old enough intel drivers on my machine to reproduce the issue. All we know at the moment is that <= .2347 is broken and >= .2993 works. I guess we should blacklist <= .2347 and see if we get more reports like this. It shouldn't be hard to bump the blacklist number up.
Comment 14•10 years ago
|
||
dupe of bug 1083071 ?
Assignee | ||
Updated•3 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•