New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 867118 link

Starred by 5 users
Status: Available
Merged: issue 897525
Owner: ----
Cc:
█ lincolnfrog@chromium.org
█ johnpallett@chromium.org
klausw@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug
Proj-VR
Proj-XR-AR
Proj-XR



Sign in to add a comment

AR camera frame stops showing after detecting surface

Project Member Reported by billorr@chromium.org, Jul 24 
From webvr slack, reported by Sorskoot.  There have been several reports of AR camera frames stopping.

I'm testing with the code from the tutorial on WebXR from Google (https://codelabs.developers.google.com/codelabs/ar-with-webxr/#1) This already has the environmentIntegration property set to true and is still giving me issues. I just hope the issue will be fixed soon...

I see the camera feed until a surface is detected. At that point I see the cubes with a teal background.

Comment 1 by billorr@chromium.org, Jul 30 

This appears to be hardware specific.  All repros so far appear to be on samsung phones, but I couldn't repro on a US S8+.  Perhaps mali related?

This also appears to only happen for some pages.

See more information: https://github.com/googlecodelabs/ar-with-webxr/issues/8

Comment 2 by billorr@chromium.org, Jul 30

Labels: -Pri-3 Pri-1

Comment 3 by billorr@chromium.org, Jul 31 

more info from linked github issue:

S8 SM-G950F with GPU: Mali-G71 MP20 Has this error.
S7 Edge: SM-G935F with GPU Mali-T880 MP12 Has this error.
S7 SM-G930F with GPU Mali-T880 MP12 Works well.

Comment 4 by sarath.s...@huawei.com, Aug 23 

Observed same gray background problem on Huawei P20 also. GPU: Mali-G72
After commenting out "this.renderer.clearDepth();" in onXRFrame(time, frame) method, demo started working fine.
Seems like some issue with the Mali drivers gl clear() or threejs.

Comment 5 by ddorwin@chromium.org, Aug 23

Cc: klausw@chromium.org lincolnfrog@chromium.org johnpallett@chromium.org
Components: Internals>XR>AR
Labels: -Pri-1 Pri-2

Comment 6 by lincolnfrog@chromium.org, Aug 29

Labels: -Pri-2 Pri-1
This seems to be reproducible enough that we should fix for launch

Comment 7 by btebbs@chromium.org, Sep 4

Labels: AR-Cleanup

Comment 8 by ericde@google.com, Sep 14 

need to understand the scope of the error as the P1, then determine how many devices are impacted (if root cause is device-based).

Comment 9 by klausw@chromium.org, Oct 30

Mergedinto: 897525
Owner: klausw@chromium.org
Status: Duplicate (was: Available)
See  issue 897525 , this should be fixed as of Canary 72.0.3590.0 which was released around Oct 25. Please let me know if it's still not working for you.

Comment 10 by billorr@chromium.org, Oct 30

Status: Available (was: Duplicate)
This is a different issue that was occurring before the single-pixel issue.  There are still workarounds in three.js and the codelabs for this issue.  This appears to be hardware-specific affecting mali, but  issue 897525  was a recent Chrome regression.

Reactivating since this is not a dupe.

Comment 11 by klausw@chromium.org, Oct 31

Owner: ----
►

Sign in to add a comment