Closed
Bug 1573616
Opened 5 years ago
Closed 5 years ago
Stop using null desc for WARP device
Categories
(Core :: Graphics, enhancement)
Core
Graphics
Tracking
()
RESOLVED
FIXED
mozilla70
| Tracking | Status | |
|---|---|---|
| firefox70 | --- | fixed |
People
(Reporter: jrmuizel, Assigned: jrmuizel)
References
Details
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
This fixes problems with mismatch that can occur when creating a content device.
|
Assignee | |
Updated•5 years ago
|
Summary: DeviceManagerDx: Use the actual adapter description instead of a null one when creating a WARP device → Stop using null desc for WARP device
|
|
Assignee | |
Comment 1•5 years ago
|
||
This makes us use the actual adapter description instead of a null one.
This fixes the problem of a mismatch being detected in ContentAdapterIsParentAdapter which
is using D3D11Checks::GetDxgiDesc to determine the adapter.
Pushed by jmuizelaar@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ae9be0ecd23a
Stop using null desc for WARP device. r=lsalzman
|
||
Comment 3•5 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox70:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla70
|
||
Updated•5 years ago
|
Assignee: nobody → jmuizelaar
You need to log in
before you can comment on or make changes to this bug.
Description
•