Closed Bug 1350794 Opened 8 years ago Closed 8 years ago

Crash when VRDisplayHost::SubmitFrame()

Categories

(Core :: WebVR, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla55
Tracking Status
firefox55 --- fixed

People

(Reporter: daoshengmu, Assigned: kip)

References

Details

Attachments

(1 file)

It's happened when calling VRDisplayHost::SubmitFrame(), and the texture from IPC has a nullptr in mTextureHost. Then, calling AutoLockTextureHostWithoutCompositor would have an assertion.
It should can be caught by our existing vr tests. Interesting to how it passes the test...
This seems to have been regressed by Bug 1343814. MozRegression points to a commit: https://hg.mozilla.org/integration/mozilla-inbound/rev/64c73abd4190
Assignee: nobody → kgilbert
Getting Closer... An earlier patch in the same bug may be responsible for the crash: https://hg.mozilla.org/integration/mozilla-inbound/rev/d55f871c503d ------------ RefPtr<ID3D11Device> DXGITextureHostD3D11::GetDevice() { if (mFlags & TextureFlags::INVALID_COMPOSITOR) { return nullptr; } - return DeviceManagerDx::Get()->GetCompositorDevice(); + return mProvider->GetD3D11Device(); }
Blocks: 1350247
No longer blocks: 1350247
Depends on: 1350247
Attachment #8851774 - Flags: review?(dvander)
Comment on attachment 8851774 [details] Bug 1350794 - Avoid dereferencing aProvider when null in DataTextureSourceD3D11 constructor https://reviewboard.mozilla.org/r/124002/#review126524
Attachment #8851774 - Flags: review?(dvander) → review+
Pushed by kgilbert@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/71dcc186d4f6 Avoid dereferencing aProvider when null in DataTextureSourceD3D11 constructor r=dvander
Pushed by kgilbert@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/16602c79bce6 Avoid dereferencing aProvider when null in DataTextureSourceD3D11 constructor
(In reply to Wes Kocher (:KWierso) from comment #7) > I had to back this out in > https://hg.mozilla.org/integration/autoland/rev/3c201a39f5df for bustage: > > https://treeherder.mozilla.org/logviewer.html#?job_id=86765716&repo=autoland I suspect the issue was that the dependent patch (which added mDevice) was in mozilla-inbound, while this one was in autoland. I've pushed to mozilla-inbound in hopes that they will land in the right order now.
Flags: needinfo?(kgilbert)
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: