New issue
Advanced search Search tips

Issue 727800 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: May 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug
Proj-XR
Proj-XR-VR



Sign in to add a comment

Screen tearing in VR browser and WebVR

Project Member Reported by klausw@chromium.org, May 30 2017

Issue description

We're seeing screen tearing in VR mode on Android/GVR/Daydream, this seems to have been triggered by http://crrev.com/725684 / r474122 which enabled using a high priority GL context for VrShellGl.

Apparently this causes conflicts with GVR's own internal high priority GL context that it uses for async reprojection.

See also b/62140262.
 

Comment 1 by klausw@chromium.org, May 30 2017

(Broken link above, should have been http://crrev.com/2902863002 .)
Project Member

Comment 2 by bugdroid1@chromium.org, May 30 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/01693c7c9e98c2a4f3809cb1b4d6ae7b97eab02f

commit 01693c7c9e98c2a4f3809cb1b4d6ae7b97eab02f
Author: klausw <klausw@chromium.org>
Date: Tue May 30 19:59:04 2017

Use standard-priority GL context for VrShellGl.

The high-priority GL context appears to be conflicting with GVR's
internal high priority context for async reprojection, so we
can't use that in other VR code.

BUG= 727800 , 725684 

Review-Url: https://codereview.chromium.org/2909163003
Cr-Commit-Position: refs/heads/master@{#475634}

[modify] https://crrev.com/01693c7c9e98c2a4f3809cb1b4d6ae7b97eab02f/chrome/browser/android/vr_shell/vr_shell_gl.cc

Comment 3 by klausw@chromium.org, May 30 2017

Labels: Merge-Request-60 OS-Android
Status: Fixed (was: Started)
Project Member

Comment 4 by sheriffbot@chromium.org, May 30 2017

Labels: -Merge-Request-60 Hotlist-Merge-Approved Merge-Approved-60
Your change meets the bar and is auto-approved for M60. Please go ahead and merge the CL to branch 3112 manually. Please contact milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), josafat@(ChromeOS), bustamante@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 5 by bugdroid1@chromium.org, May 30 2017

Labels: -merge-approved-60 merge-merged-3112
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/05bac91e966e8be06039390c1cb44a51f0e5957f

commit 05bac91e966e8be06039390c1cb44a51f0e5957f
Author: klausw <klausw@chromium.org>
Date: Tue May 30 21:18:04 2017

Use standard-priority GL context for VrShellGl.

The high-priority GL context appears to be conflicting with GVR's
internal high priority context for async reprojection, so we
can't use that in other VR code.

BUG= 727800 , 725684 
NOTRY=true
NOPRESUBMIT=true

Review-Url: https://codereview.chromium.org/2909163003
Cr-Original-Commit-Position: refs/heads/master@{#475634}
Review-Url: https://codereview.chromium.org/2909393002
Cr-Commit-Position: refs/branch-heads/3112@{#40}
Cr-Branched-From: b6460e24cf59f429d69de255538d0fc7a425ccf9-refs/heads/master@{#474897}

[modify] https://crrev.com/05bac91e966e8be06039390c1cb44a51f0e5957f/chrome/browser/android/vr_shell/vr_shell_gl.cc

Status: Verified (was: Fixed)
Hi Klaus, I verified this by testing 60.0.3112.78 using our webvr samples pages on a Pixel with the Daydream headset, and ensured I did not notice any screen tearing. And also by testing wikipedia.org in VR browser. Please let me know if there are other ways I would need to verify. Thanks!

Comment 7 by klausw@chromium.org, Jul 26 2017

@dbbrooks, thank you for verifying. That should be sufficient, I'm pretty confident that the context priority conflict was the cause of tearing and that the change from comment #5 fixed it, and I also haven't seen it myself in further testing.
Components: Blink>WebXR

Sign in to add a comment