Closed Bug 1084239 Opened 10 years ago Closed 6 years ago

WebGL doesn't work with Firfeox33 and Q45 chipset. (With Firefox32 it works fine)

Categories

(Core :: Graphics: CanvasWebGL, defect)

33 Branch
x86_64
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: benedikt.schindler, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0 Build ID: 20141011015303 Steps to reproduce: Firefox: 33 OS : Windows7 / WindowsXP Graphix: Intel Q45 onboard chipset - After installing FF33 the browser didn't give me a WebGL context. - When i reinstalled FF32 i could get a WebGL context, and everything works without any additional steps. - I installed FF3 again. And the WebGL context was gone again. After a graphic driver update the results are different in WinXP and Win7. With Win7: - I could get a default WebGL context. - But it couldn't get WebGL context, if the attribute stencil=true. Win XP: - As Administrator: i could get a default WebGL context - As Administrator: i couldn't get a WebGL context, if the attribute stencil=true. - As normal User: i couldn't get a WebGL context at all. And again with FF32 all works fine without driver update and for all users. Actual results: I didn't get any webGL context Expected results: I should get a webGL context.
Component: Untriaged → Canvas: WebGL
Product: Firefox → Core
Did you test with a clean profile? https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles In addition, could you type about:support and paste the "graphics" section (Win XP). Last question, could test with OMTC disabled (about:config > layers.offmainthreadcomposition.enabled = false) (restart FF to apply)
Flags: needinfo?(benedikt.schindler)
Sorry for the big delay. 1.) clean profile - doesn't help 2.) layers.offmainthreadcomposition.enabled = false - doesn't help 3.) graphic section within Firefox 32 DirectWrite aktiviert false (0.0.0.0) Geräte-ID 0x2e12 GPU #2 aktiv false GPU-beschleunigte Fenster 1/1 Direct3D 9 Karten-Beschreibung Intel(R) Q45/Q43 Express Chipset Karten-RAM Unknown Karten-Treiber igxprd32 Treiber-Datum 7-23-2012 Treiber-Version 6.14.10.5420 Vendor-ID 0x8086 WebGL-Renderer Google Inc. -- ANGLE (Intel(R) Q45/Q43 Express Chipset Direct3D9 vs_3_0 ps_3_0) windowLayerManagerRemote false AzureCanvasBackend skia AzureContentBackend cairo AzureFallbackCanvasBackend cairo AzureSkiaAccelerated 0 3.) graphic section within Firefox 33 - changes to 32 windowLayerManagerRemote true - And then there is the problematic line in Firefox 33 : Direct2D aktiviert Wurde auf Grund Ihrer Grafiktreiberversion blockiert. (free translated into english): Direct2D activated Blocked because of garphic driver version. So, FF32 is able to work with my driver and FF33 isn't.
Flags: needinfo?(benedikt.schindler)
Because of my reinstalling FF32 with the FF32.0b9.exe , i ended up on the Beta-Update-Channel. So now FF updated itself to FF34. With the FF34 of the beta update channel, WebGL works fine again. The about:support graphic section shows the same parameters as the version FF33. It also contains the line that Direct2D is deactivated. Is Direct2D not needed for WebGL or is FF34 ignoring that fact because it is a beta version? btw: i didn't find a newer driver for that garphic card.
That is only the driver for Win7 And that is the driver i have installed in the Win7 machine. And there the context doesn't work with stencil=true. (But it worked in FF32.) For WinXP 32Bit there is no newer driver for the chipset. 14.42.15.5420(6.14.10.5420) With FF32 i had an older driver installed and it worked fine. I only updated to that driver because of the problems with FF33. I mean there must be a reason why the driver/chipset was added to the Direct2D blacklist in FF33. And because of the working FF34 version i think Direct2D isn't needed for WebGL.
Very similar to Bug 1085153 WebGL is not working in FF33+ for many Windows users with older Intel and ATI hardware.
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.