Problem with WebGL on Windows in chromium 128

[Andy Skinner]

We use the chromium embedded framework in our product, and are updating from version 118 to 128.  On Windows, WebGL is not working for us.  We have removed our own code from the picture by opening up webglreport.com in a window.  Sometimes it says that WebGL is disabled or unavailable.  When it says it is available, it is SwiftShader instead of using the hardware acceleration.

We have seen WebGL with hardware work for both linux and mac.  We did get hardware acceleration on Windows with the previous version as well.

Any ideas why it would not work, or how to go about debugging it?

I am not familiar with CEF, and the team doing the updating isn't familiar with WebGL, so we may need to collaborate to investigate further.

Thanks,

andy

[Kai Ninomiya]

If you can open about:gpu (chrome://gpu) the same way, it should provide some info about why WebGL is unavailable.

Because it's inconsistent, my first suspicion would be that there are GPU process crashes. That's probably something you can detect already, but chrome://gpu logs will indeed log that info, if it's happening. ("GpuProcessHost: The GPU process crashed!") This can be emulated by opening about:gpucrash

-Kai (he/they)

--
You received this message because you are subscribed to the Google Groups "WebGL Dev List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to webgl-dev-lis...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/webgl-dev-list/af3bcbb1-3cea-4a1b-860e-c46760752b0cn%40googlegroups.com.

[Andy Skinner]

Thanks, that is interesting.  We do have this at the bottom:

GpuProcessHost: The GPU process crashed!
GpuProcessHost: The GPU process crashed!
GpuProcessHost: The GPU process crashed!

Does that happen before it gathers info?  Is that crash cause or effect?  Are those multiple crashes, or multiple reports?

There is a Problems Detected section:

*   WebGPU has been disabled via blocklist or the command line.
    Disabled Features: webgpu

*   WebGL2 has been disabled via blocklist or the command line.
    Disabled Features: webgl2

*   Accelerated rasterization has been disabled, either via blocklist, about:flags or the command line.
    Disabled Features: rasterization

*   Accelerated video encode has been disabled, either via blocklist, about:flags or the command line.
    Disabled Features: video_encode

*   Accelerated video decode has been disabled, either via blocklist, about:flags or the command line.
    Disabled Features: video_decode

*   WebGL has been disabled via blocklist or the command line.
    Disabled Features: webgl

*   Gpu compositing has been disabled, either via blocklist, about:flags or the command line. The browser will fall back to software compositing and hardware acceleration will be unavailable.
    Disabled Features: gpu_compositing

*   Accelerated 2D canvas is unavailable: either disabled via blocklist or the command line.
    Disabled Features: 2d_canvas

As well as a Problems Detected for Hardware GPU:

Problems Detected for Hardware GPU
==================================
*   Some drivers are unable to reset the D3D device in the GPU process sandbox
    Applied Workarounds: exit_on_context_lost

*   Unpacking overlapping rows from unpack buffers is unstable on NVIDIA GL driver:
    (http://crbug.com/596774)
    Applied Workarounds: unpack_overlapping_rows_separately_unpack_buffer

*   Disable KHR_blend_equation_advanced until cc shaders are updated:
    (http://crbug.com/661715)
    Applied Workarounds: disable(GL_KHR_blend_equation_advanced),
        disable(GL_KHR_blend_equation_advanced_coherent)

*   VPx decoding isn't supported well before Windows 10 creators update.:
    (http://crbug.com/616318), (http://crbug.com/667532)
    Applied Workarounds: disable_accelerated_vp8_decode,
        disable_accelerated_vp9_decode

*   Expose WebGL's disjoint_timer_query extensions on platforms with site isolation:
    (http://crbug.com/808744), (http://crbug.com/870491)
    Applied Workarounds: enable_webgl_timer_query_extensions

*   Disable GL_MESA_framebuffer_flip_y for desktop GL:
    (http://crbug.com/964010)
    Applied Workarounds: disable(GL_MESA_framebuffer_flip_y)

*   VP8 decoding crashes before Windows 10 Fall Creators Update.:
    (http://crbug.com/1094840)
    Applied Workarounds: disable_accelerated_vp8_decode

*   Disable VP9 k-SVC video decoding on non-Intel GPUs:
    (http://crbug.com/1508379)
    Applied Workarounds: disable_d3d11_vp9_ksvc_decoding

*   Block all NPU drivers until newer versions work with WebNN:
    (http://crbug.com/341327464)
    Applied Workarounds: disable_webnn_for_npu