Chrome GPU Process Crash on Chrome + M4 Mac #389
Description
Description
Shortly after loading any Rive file using v2.27.1 of the WebGL v2 renderer, the Chrome GPU Process Host crashes, the browser refreshes ALL Windows, and the WebGLv2 context becomes unavailable until the browser is restarted.
Provide a Repro
This can be produced on an M4 Mac on Chrome 136.0.7103.49 with the latest version of the Rive renderer (webgl 2.0) by loading any rive file in the new renderer. Shortly after the file is loaded, the WebGL process crashes - with no additional messages logged to the console.
It looks like the suspect configuration may be:
VENDOR= 0x106b [Google Inc. (Apple)], DEVICE=0x0000 [ANGLE (Apple, ANGLE Metal Renderer: Apple M4 Pro, Version 15.4.1 (Build 24E263))], DRIVER_VENDOR=Apple, DRIVER_VERSION=15.4.1 ACTIVE
The WebGL1 and Canvas renderers work OK.
Expected behavior
Should not crash.
Browser & Versions (please complete the following information)
- Browser: 136.0.7103.49 (stock / no plugins)
- OS: macOS 15.4.1
Let me know if there is any additional diagnostic details or if anyone else can reproduce on an M4 mac with the latest version of Chrome. It's OK in Safari and on another M1 mac. This still reproduces after a reboot.
GPU LOG @ chrome://gpu/
GpuProcessHost: The GPU process crashed!
GpuProcessHost: The GPU process crashed!
GpuProcessHost: The GPU process crashed!
GpuProcessHost: The GPU process crashed!
[8691:390338:0505/184621.930719:WARNING:ui/gl/angle_platform_impl.cc:54] : Debug.cpp:186 (insertMessage): GL error: HIGH: Error: 0x00000502, in ../../third_party/angle/src/libANGLE/renderer/metal/mtl_pipeline_cache.mm, CreateRenderPipelineState:122. Internal error. Metal error: Fragment shader does not write to render target color(0), index(0) that is required for blending