898386 - WebGL2 bug report -Firefox crashes in mozilla::WebGLContext::GenerateWarning with "MOZ_WEBGL_FORCE_OPENGL=1"

Status: RESOLVED INCOMPLETE

(Core :: Graphics: CanvasWebGL, defect)

Description

[cstein]

Attachment: crash-report.txt

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.72 Safari/537.36

Steps to reproduce:

I am trying to create the "experimental-webgl2"-Context as shown in the tutorial on Win7 64bit and with the newest nightly build. 





Actual results:

Without MOZ_WEBGL_FORCE_OPENGL=1 the context creation stops with:

Error: WebGL: Error during ANGLE OpenGL ES initialization 

With the flag set firefox crashes when opening the resprective local page.
The crash-report is attached. 

I am guessing the problem could be connected to my graphics adapter combination with optimus technologie - i might further investigate this later today.


Expected results:

WebGL2 Context should have been created successfully.

Comment 1

[Scoobidiver (away)]

Please provide the crash ID from about:crashes.

Comment 2

[cstein]

cdf48199-5977-4a0a-be62-4a9d12130726

Comment 3

[Scoobidiver (away)]

Here is the crash report link: bp-cdf48199-5977-4a0a-be62-4a9d12130726.

(In reply to cstein from comment #0)
> Without MOZ_WEBGL_FORCE_OPENGL=1 the context creation stops with:
> Error: WebGL: Error during ANGLE OpenGL ES initialization 
> With the flag set firefox crashes when opening the resprective local page.
> The crash-report is attached.
I am surprised because for Nvidia Optimus OpenGL is used by default. See https://wiki.mozilla.org/Blocklisting/Blocked_Graphics_Drivers#NVIDIA_cards

Comment 4

[cstein]

Hm, the crash being connected to optimus was just a guess by me, because i had some trouble with this combination in the past already.

Comment 5

[cstein]

https://wiki.mozilla.org/Platform/GFX/WebGL2#Playground says that 
" Actually, we are running WebGL on an ANGLE context that convert OpenGL ES 2 function calls to DirectX 11 calls."

And the nvidia link says:
"On Optimus devices, ANGLE rendering for WebGL is blocked (bug 636870). So WebGL should still work, but will use the OpenGL driver."

So it seems as long as the webgl2 context uses ANGLE it won't work for optimus devices ?

Comment 6

[Guillaume Abadie]

Sorry for late, didn't see this bug. The WebGL 2 initialization mechanism has completely changed since. Do you still have the crash?

Comment 7

[Guillaume Abadie]

(In reply to cstein from comment #5)
> https://wiki.mozilla.org/Platform/GFX/WebGL2#Playground says that 
> " Actually, we are running WebGL on an ANGLE context that convert OpenGL ES
> 2 function calls to DirectX 11 calls."
> 
> And the nvidia link says:
> "On Optimus devices, ANGLE rendering for WebGL is blocked (bug 636870). So
> WebGL should still work, but will use the OpenGL driver."
> 
> So it seems as long as the webgl2 context uses ANGLE it won't work for
> optimus devices ?
Actually, It is impossible to get a WebGL 2 context running on ANGLE regardless the hardware, because the ANGLE implementation do not provide GL_GPU_shader4. That why the MOZ_WEBGL_FORCE_OPENGL=1 is required on Windows.

Comment 8

[cstein]

Hey, i just updated the nightly and it's still crashing when i try to create the context. Did i get that right, that it is not running on ANGLE any more ?

Comment 9

[Guillaume Abadie]

(In reply to cstein from comment #8)
> Hey, i just updated the nightly and it's still crashing when i try to create
> the context. Did i get that right, that it is not running on ANGLE any more ?

The thing is WebGL 2 has never ever worked on ANGLE because we are using GPU_shader4 till the very begining like it says in "Playground - Available features timeline".

Would you be possible to run a debug nightly into a debugger, and see where it crashes? A stack trace would be nice.

http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2013-08-28-mozilla-central-debug/

Thank you!

Comment 10

[cstein]

Attachment: firefox-debug_14dc_2013-08-29_12-01-51-494.log

Comment 11

[cstein]

I followed the steps from : 
https://developer.mozilla.org/en-US/docs/How_to_get_a_stacktrace_with_WinDbg

But it seemed like the symbols could not be loaded, though i made sure that the "Work offline" was unchecked. 

When firefox started the console output said something about no GL acceleration being available.

Comment 12

[cstein]

I added a second log file.

Symbol error:
.*** ERROR: Symbol file could not be found.  Defaulted to export symbols for firefox.exe - 

GL Error:
[JavaScript Warning: "Error: WebGL: WebGL 2 requires GL_EXT_gpu_shader4!

Access Violation:
(1e28.1e2c): Access violation - code c0000005 (first chance)

Comment 13

[cstein]

Attachment: firefox-debug_1d78_2013-08-29_12-59-00-225.log

Comment 14

[u279076]

It's been over two years, does this still reproduce?

Comment 15

[Phoenix]

Resolved per whiteboard