New issue
Advanced search Search tips

Issue 726374 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jun 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug
Proj-XR



Sign in to add a comment

WebVR: use optimized render path by default

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

Issue description

WebVR supported two variants for synchronizing cross-process image transfer via mailbox. The intended path was to defer waiting for transfer confirmation until the next frame to avoid blocking the Javascript thread unnecessarily, but this was causing flickering (black frames), so the default was to use the slower path with waiting after submitting.

Now that the underlying synchronization is fixed (see  issue 723962  and crrev.com/2891033002 / r473687), we want to use the faster path by default.

 
Project Member

Comment 1 by bugdroid1@chromium.org, May 25 2017

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

commit 89f6d708d1be7d2c1cebaa74b11908740130f617
Author: klausw <klausw@chromium.org>
Date: Thu May 25 18:57:24 2017

WebVR: use optimized render path with deferred wait

Now that the synchronization issue (occasional black screen flashes) that
affected the optimized render path is fixed (see  issue 723962  and
crrev.com/2891033002 / r473687), switch to that implementation and
remove the old code path.

BUG= 726374 

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

[modify] https://crrev.com/89f6d708d1be7d2c1cebaa74b11908740130f617/third_party/WebKit/Source/modules/vr/VRDisplay.cpp

Status: Fixed (was: Started)
Components: Blink>WebXR

Sign in to add a comment