WebXR AR camera access crashes the page since the latest Google Chrome 147+ for Android

[m0nzderr]

Description

Since the recent Google Chrome release 147 for Android, accessing camera texture under immersive AR session crashes the page ("Aw, snap" error). Just tested on several different devices from different vendors (Samsung, Motorola). Same crash happens in Chrome Beta 148.
Camera access still works normally after downgrading to previous Chrome versions (146 and below).

The crash occurs at renderer.xr.getCameraTexture( view.camera ); (same result if calling glBinding.getCameraImage directly).
Check the official three.js example for this behavior: https://threejs.org/examples/webxr_ar_camera_access.html

Why do I think this might an issue with THREE.js?
There is another vanilla WebXR camera access example that does not crash on Chrome 147+: https://storage.googleapis.com/chromium-webxr-test/r1516914/proposals/camera-access-barebones.html .
Essentially it does the same thing as the WebXRManager when configuring session, creaing glBinding and layers, but probably in a different order that does not lead to a crash.

Reproduction steps

1. Make sure the recent release of Google Chrome for Android is installed (e.g., 147.0.7727.101, or 148 beta)
2. Open the example page https://threejs.org/examples/webxr_ar_camera_access.html (e.g., from three.js v184 release or earlier)
3. Start AR and observe the crash page ("Aw, snap").

Code

// see https://threejs.org/examples/webxr_ar_camera_access.html

Live example

• joffical three.js example: https://threejs.org/examples/webxr_ar_camera_access.html

• vanilla WebXR example: https://storage.googleapis.com/chromium-webxr-test/r1516914/proposals/camera-access-barebones.html

Screenshots

https://threejs.org/examples/webxr_ar_camera_access.html :

https://storage.googleapis.com/chromium-webxr-test/r1516914/proposals/camera-access-barebones.html :

Version

r184

Device

Mobile

Browser

Chrome

OS

Android

[shub3dfe]

I am facing a similar issue.

[m0nzderr]

UPD: Taking a closer look at WebXRManager implementation I found a way of preventing the crash by forcing it to use the the XRWebGLLayer instead of XRProjectionLayer, regardles of the 'createProjectionLayer' feature available. E.g, by switching supportsLayers to false at WebXRManager.js:426. Still not sure what the side effects of this change are, but my AR camera access code seems to stop crashing on Chrome 147.

[Mugen87]

I can reproduce on a Pixel 8a. I've tried to investigate the problem via Remote debugging but since the tab crashes, I see nothing in the browser console.

@cabanier Should this breakage be reported to the Chromium bug tracker? The OP mentions setting below flag to false fixes the issue as a workaround.

three.js/src/renderers/webxr/WebXRManager.js

Lines 424 to 426 in 3105f51

	// Check that the browser implements the necessary APIs to use an
	// XRProjectionLayer rather than an XRWebGLLayer
	const supportsLayers = supportsGlBinding && 'createProjectionLayer' in XRWebGLBinding.prototype;

[cabanier]

@toji implemented projection layers support in Chrome. I suspect that this triggers that bug.
I don't have a pixel to try this out myself. @alcooper might also be a good contact here since he's one of the engineers on WebXR.
If they don't respond, yes please file a bug on crbug.com

[TxMindWire]

Got the same issue on my Samsung A54. Funny thing is, it crashes only on versions of THREE above 177. Reverted to 177 and everything works fine. After putting log from ADB logcat into gemini it "thinks" what problem lies in camera. Like WebXR requested it, while it was already in use (no, I had nothing running in the background)

Here is highlight from ADB that gemini pointed me to

`04-19 23:58:56.426 20572 20582 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr --------

04-19 23:58:56.426 20572 20582 F DEBUG : Cause: null pointer dereference

04-19 23:58:56.426 20572 20582 F DEBUG : x0 0000000000000000 x1 0000007174e544ec x2 0000007174e54548 x3 000018821fdf3149`

Can post full log, but for me its borderline unreadable

[m0nzderr]

@TxMindWire , did not test on threejs v16x-v17x range, but I'm definitely getting the same tab crash on my legacy code that uses three.js v158.

For those how are looking for quick workaround for the problem that works both with threejs r158 and r184:

        delete XRWebGLBinding.prototype.createProjectionLayer; // for r184 
        delete XRRenderState.prototype.layers; // for r158

Make sure to execute it once, before setting up the webxr session. It just makes it look like the projection layers are not supported.

ED: This is a temporary fix for Chromium that might break webxr on other devices, take necessary precautions

[cabanier]

Make sure to execute it once, before setting up the webxr session. It just makes it look like the projection layers are not supported.

This will break layers support on Quest. Please don't make that change blindly.

[shub3dfe]

Hey everyone, does this fix need to be done in threejs or Chromium? If this fix is threejs side, I am happy to work on it.

[Mugen87]

When I understand the issue correctly, the root cause is on the Chromium side.

[alcooper91]

@alcooper might also be a good contact here since he's one of the engineers on WebXR. If they don't respond, yes please file a bug on crbug.com

Sorry, looks like you tagged not-me (though I was out anyways). Has anyone filed a crbug for this issue yet? I don't think I've seen it.