model-viewer
model-viewer copied to clipboard
google
Exiting a WebXR session freezes Chrome entirely on some devices
Description
May be related to https://github.com/google/model-viewer/issues/2780
When entering a session and then exiting it, we see some devices that simply freeze. I believe this is outside model-viewers reach (we're also seeing it with basic samples) but since it also affects model-viewer and usage is so high, I thought it's good to track it here.
- There is no crash log in chrome://crashes - seems browser freezes and not crashes
- There is no reaction from the browser anymore; the last rendered image is frozen until force qutting the Chrome app
- It does not happen each time, it happens randomly; seems ~20-30% of the time. Often enough to be really annoying
cc @klausw @elalish
Live Demo
Reproduces on the start page on https://modelviewer.dev on Google Pixel 4a
Browser Affected
- [X] Chrome, version: 107.0.5304.105 (but happened for at least a couple months now)
OS
- [X] Android
AR
- [X] WebXR
@hybridherbst - one question: what Android version is this happening on?
(but happened for at least a couple months now)
Did you by any chance upgrade your OS prior to the issue appearing?
@ronpadz - ditto, what Android version is your Pixel 6 Pro running?
For context, I took a stab at trying to investigate this and I have a very weak suspicion that it may be related to Android version.
Same issue on Chrome 113 Android 13 Samsung Galaxy A32, exactly what @hybridherbst described.
I didn't reproduce the issue using the back button. I have the issue only with the x button 20-30% of the time. It was with model-viewer 3.1.1.
Is there an open issue on chromium tracker about this? I couldn't find anything related to this searching for webxr here https://bugs.chromium.org/p/chromium/issues/list?q=webxr&can=2
I didn't reproduce the issue using the back button. I have the issue only with the x button 20-30% of the time. It was with model-viewer 3.1.1.
Actually I just reproduced the issue with the back button as well.
I reported it at https://bugs.chromium.org/p/chromium/issues/detail?id=1446911 I took the liberty to copy and paste your description @hybridherbst If you have another phone model / Android version where you have the issue, please add a comment there. If you have a phone model / Android version where you never had the issue, this would be interesting to know too.
The issue may not be the Android version, I tested on my old S8 Android 9, it was working great with Chrome 102, no crash after 30 enter-exit, I updated to Chrome 113, it was more and more slow and it crashed after the 13th times, see my comments on the issue. Next step would be to test old Chrome versions between 102 and 107 to pin point the issue I guess.
On the latest canary, does this still repro if you go into chrome://flags and disable the "WebXR Shared Buffers" flag?
@alcooper91 I just tested Chrome Canary 115.0.5786.0 on my Samsung A32. with "WebXR Shared Buffers" enabled (Default), it froze after the 4th time with "WebXR Shared Buffers" disabled, it froze after the 3rd time, sometimes the page refreshes (I see the loading indicator in model-viewer) after the 12th time, and then froze at 16th times, it's all random.
I tested several Chrome versions (109-113, see issue) on the S8, I don't really reproduce the same issue than with the A32, so the issue may be related to the Android version in the end. On A32, it froze Chrome after exiting the AR session the second time with Chrome Canary 116.0.5794.2