Closed
Bug 1297105
Opened 9 years ago
Closed 9 years ago
Invalid array access in mozilla::gfx::impl::VRDisplayOculus::GetNextRenderTarget()
Categories
(Core :: Graphics, defect)
Tracking
()
RESOLVED
FIXED
mozilla51
| Tracking | Status | |
|---|---|---|
| firefox51 | --- | fixed |
People
(Reporter: mccr8, Assigned: kip)
References
Details
(Keywords: crash)
Crash Data
Attachments
(1 file)
This bug was filed from the Socorro interface and is
report bp-a133d36c-1e68-440e-aab6-670a82160821.
=============================================================
Here's a second report:
bp-8d3e723f-a8fe-4431-8137-f54732160818
| Reporter | ||
Comment 1•9 years ago
|
||
Bug 1159244 added a release assert to array bounds checking. Can you take a look at this, Kip? Thanks.
Flags: needinfo?(kgilbert)
| Assignee | ||
Comment 2•9 years ago
|
||
I'll investigate, thanks!
Assignee: nobody → kgilbert
Flags: needinfo?(kgilbert)
| Reporter | ||
Comment 3•9 years ago
|
||
Under the metadata tab, these crashes both have: "ElementAt(aIndex = 0, aLength = 0)". So the code is attempting to access index 0 of an empty array.
| Assignee | ||
Comment 4•9 years ago
|
||
This may be happening if the DX11 objects are failing to be created for blitting the Oculus headset texture, resulting in this array not being populated. Patch is incoming...
| Comment hidden (mozreview-request) |
| Comment hidden (mozreview-request) |
| Assignee | ||
Updated•9 years ago
|
Attachment #8786519 -
Flags: review?(continuation)
| Reporter | ||
Comment 7•9 years ago
|
||
| mozreview-review | ||
Comment on attachment 8786519 [details]
Bug 1297105 - Prevent crash when DX11 resources fail to be allocated for Oculus VR HMD presentation
https://reviewboard.mozilla.org/r/75440/#review74424
Looks reasonable to me.
::: gfx/vr/gfxVROculus.cpp:768
(Diff revision 2)
> + * XXX - We should resolve fail the promise returned by
> + * VRDisplay.requestPresent() when the DX11 resources fail allocation
> + * in VRDisplayOculus::StartPresentation().
> + * Bailing out here prevents the crash but content should be aware
> + * that frames are not being presented.
> + * See Bug 1299309
nit: This should have a period at the end.
Attachment #8786519 -
Flags: review?(continuation) → review+
| Reporter | ||
Updated•9 years ago
|
Crash Signature: [@ InvalidArrayIndex_CRASH] → [@ InvalidArrayIndex_CRASH] [@ InvalidArrayIndex_CRASH | mozilla::gfx::impl::VRDisplayOculus::GetNextRenderTarget ]
| Comment hidden (mozreview-request) |
Pushed by kgilbert@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/a3c6df384b47
Prevent crash when DX11 resources fail to be allocated for Oculus VR HMD presentation r=mccr8
Comment 10•9 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla51
You need to log in
before you can comment on or make changes to this bug.
Description
•