New issue
Advanced search Search tips

Issue 793725 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 753865
Owner: ----
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug
Proj-VR
Proj-XR



Sign in to add a comment

WebVR crashes Chrome on Android (Samsung Note 8)

Reported by masterdo...@gmail.com, Dec 11 2017

Issue description

Steps to reproduce the problem:
1. Samsung Note 8 default display resolution FHD+ crashes (WQHD+ works)
2. Go into WebVR mode pretty much any where
3. watch it silently crash not show stereo 3D images for cardboard etc.) and reloads tab

What is the expected behavior?
The Samsung Note 8 comes with a Default Display Setting that crashes the WebVR driver in Chrome when switching to that kind of content (Nougat 7.1.1).
After switching to WQHD+ the Full maximum true resolution of the device, it will work correctly and provide stereo images for Cardboard etc. so it's easily (with device possibly others) testable and repeatable.

I have provided this THREE js example but it's the same for Daydream etc. and all other tools code bases etc.
https://threejs.org/examples/?q=webvr#webvr_cubes

In the example it's when you select the botton center bottom that says "Enter VR". 
If the display setting on Android 7.1.1 is in FHD+ it crashes in WQHF+ is works correctly.

What went wrong?
The browser silently crashes and reloads a stereo WebVR experience if the display is in default (middle) mode.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 62.0.3202.84  Channel: stable
OS Version: 7.1.1
Flash Version: 

I'm hopeful you can pass on the bug to Android OS people and in turn Samsung if that is where the problem lies.
It looks like a Nougat Display Driver issue, alas the first line of defense to check is Chrome Stable. I tried reporting this in the Issue Tracker issuetracker.google.com and it said to report WebVR bugs here instead but it's not a new feature anymore so that's probably wrong now too.
 
This tracker needs an edit mode.
Bug initially reported and eventually discovered after a week of soul searching here.
https://github.com/mrdoob/three.js/issues/12789

I've also just received an Android OS update and applied it. This did not correct the problem. Same Droid Version 7.1.1 with Samsung Experience 8.5 I don't think that changed either, so it applies to all version I suppose. Kernel 4.4.21-12461033 dpi@SWDG5307 #1 Nov 14 2017
Labels: Needs-Feedback
I believe this is a duplicate of  issue 753865 . Can you please try updating to Chrome M63 (which I believe has shipped to the stable channel) and see if the problem is resolved for you?

If you need to use Chrome M62 for some reason, you'll have to use your noted workaround of changing the resolution.
Yes 63.0.3239.83 auto-updated and WebVR seems to work at default resolution FHD+ on the Samsung Note8 now. Thank you.
Project Member

Comment 5 by sheriffbot@chromium.org, Dec 13 2017

Cc: mthiesse@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "mthiesse@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Mergedinto: 753865
Status: Duplicate (was: Unconfirmed)
Components: Blink>WebXR

Sign in to add a comment