Closed Bug 1426031 Opened 6 years ago Closed 6 years ago

Ensure gfxVRGVR SubmitFrame is called on the correct thread

Categories

(Core :: WebVR, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla59
Tracking Status
firefox59 --- fixed

People

(Reporter: rbarker, Assigned: rbarker)

Details

Attachments

(1 file)

The addition of the VRThread broke gfxVRGVR. All GoogleVR rendering calls must be made on the same thread that the library was initialized on. VRDisplayHost::SubmitFrameInternal() needs to be invoked on the Compositor Thread for the GVR implementation.
Assignee: nobody → rbarker
Summary: Ensure gvVRGVR SubmitFrame is called on the correct thread → Ensure gfxVRGVR SubmitFrame is called on the correct thread
Comment on attachment 8937619 [details]
Bug 1426031 - Ensure gfxVRGVR SubmitFrame is called on the correct thread

https://reviewboard.mozilla.org/r/208290/#review214060

lgtm. thank!
Attachment #8937619 - Flags: review?(dmu) → review+
We are going to separate our VR module into a separate process in January. I encourage you to enable our vr reftest on Android to avoid this kind of regression in the future.
(In reply to Daosheng Mu[:daoshengmu] from comment #3)
> We are going to separate our VR module into a separate process in January. I
> encourage you to enable our vr reftest on Android to avoid this kind of
> regression in the future.

I've already spoken to :kip about this, Android can not have its GVR implementation moved into a separate process. The GVR API must always be invoked within the same thread (the controller API is the sole exception) and those threads must be in the same process as the UI Thread. Of course SVR and Oculus Mobile will add additional wrinkles as they are added.

Currently we can not build GeckoView with GVR enabled on test machines and even if we could, would require a pixel to run. The reftests using the PuppetVR class would not have caught this. In the future it would probably be beneficial to include me when making architectural changes so I can provide feedback on how it will affect mobile.
Pushed by rbarker@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/e9d182f7c389
Ensure gfxVRGVR SubmitFrame is called on the correct thread r=daoshengmu
https://hg.mozilla.org/mozilla-central/rev/e9d182f7c389
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla59
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: