Closed
Bug 1383590
Opened 8 years ago
Closed 8 years ago
Crash in CContext::ID3D11DeviceContext1_SetShaderResources_<T>
Categories
(Core :: Graphics: Layers, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1382829
People
(Reporter: n.nethercote, Unassigned)
Details
(Keywords: crash)
Crash Data
This bug was filed from the Socorro interface and is
report bp-b84e39d0-4ab4-4b49-ade3-87bb60170723.
=============================================================
This is the #8 Windows topcrash in Nightly 20170721030204 builds. This signature has been seen in very small numbers in older versions, but there is a spike starting in Nightly 20170718030207 which feels like it has a new root cause. The regression window for that build is here:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=aff336ac161daa3ea350e59a288963edbd58ed39&tochange=5e73b9798464c3f7106f0161dc9a49b234f42f9c
From that list I think it might be bug 1377595 or bug 1375461, but I'm not confident about either.
nical, bas, what do you think?
Flags: needinfo?(nical.bugzilla)
Flags: needinfo?(bas)
|
||
Comment 1•8 years ago
|
||
I am pretty certain bug 1377595 isn't related to this. I am not familiar with the advanced layers code where this is crashing (Bas will know). It could be that we are passing a null pointer to one of the parameters that PSSetShaderResources expects to be non null.
Flags: needinfo?(nical.bugzilla)
|
||
Updated•8 years ago
|
Group: gfx-core-security
Flags: needinfo?(dvander)
|
|
||
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
|
||
Updated•5 years ago
|
Group: gfx-core-security
You need to log in
before you can comment on or make changes to this bug.
Description
•