Closed
Bug 1259548
Opened 9 years ago
Closed 8 years ago
Forcing WARP gives lots of rendering artifacts on Windows 10
Categories
(Core :: Graphics: Layers, defect)
Core
Graphics: Layers
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: jrmuizel, Unassigned)
Details
(Whiteboard: gfx-noted)
Setting layers.d3d11.force-warp to true on Windows 10 gives all kinds of rendering artifacts.
Reporter | ||
Updated•9 years ago
|
Keywords: regression,
regressionwindow-wanted
Comment 1•9 years ago
|
||
Hi,
I ran mozregression to try and find a window for this issue, but since the last know good build is from 2014-12-15, the taskclusters for inbound no longer exist.
Last good revision: f14dcd1c8c0b (2014-12-15)
First bad revision: b836016d82b5 (2014-12-16)
Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=f14dcd1c8c0b&tochange=b836016d82b5
Out of this pushlog the only thing that stands out to me is Bug 1088414.
Thanks,
Cipri
Keywords: regressionwindow-wanted
Comment 2•9 years ago
|
||
(In reply to Jeff Muizelaar [:jrmuizel] from comment #0)
> Setting layers.d3d11.force-warp to true on Windows 10 gives all kinds of
> rendering artifacts.
Are you remembering to also disable Direct2D? WARP with D2D isn't really a tested config.
Flags: needinfo?(jmuizelaar)
Whiteboard: gfx-noted
Comment 4•9 years ago
|
||
Setting gfx.direct2d.disabled to true does seem to make the issue go away.
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Updated•8 years ago
|
Keywords: regression
You need to log in
before you can comment on or make changes to this bug.
Description
•