Color fringing/image corruption on Windows provided driver 22.19.162.4 for Radeon RX 560
Categories
(Core :: Graphics: WebRender, defect, P2)
Tracking
()
People
(Reporter: yoasif, Assigned: Gankra)
References
Details
Attachments
(5 files)
Reported on reddit: https://www.reddit.com/r/firefox/comments/ddidht/firefox_greenpink_textimages_glitch_how_do_i_fix/
The driver seems to be the latest provided by Windows Update. Updating the driver to the latest provided by the vendor seems to resolve the issue.
Reporter | ||
Comment 1•5 years ago
|
||
Reporter | ||
Comment 2•5 years ago
|
||
Reporter | ||
Comment 3•5 years ago
|
||
Reporter | ||
Comment 4•5 years ago
•
|
||
[Tracking Requested - why for this release]:
WebRender on AMD is enabled by default now in release, Windows Update driver is affected.
Comment 5•5 years ago
|
||
We have RX 460 that we'll try to reproduce it on.
Assignee | ||
Comment 6•5 years ago
|
||
This looks like the return of Bug 1565663, which we also failed to reproduce with the RX 460.
Last time we closed it after the user updated their ~2017 driver and it went away. It seems the exact same thing happened here.
Also interesting is that in the old version, it was actually happening regardless of Webrender (for some users?).
Assignee | ||
Comment 7•5 years ago
|
||
In that previous report it was also Driver 22.19.162.4, which suggests we should maybe blacklist this exact driver?
Assignee | ||
Comment 8•5 years ago
|
||
Hey darkspirit, you were able to reproduce some of the similar issues reported, right? Or were those just A Different But Similar Bug?
Comment 9•5 years ago
|
||
Too late to do anything about it in 69 at this point.
Comment 10•5 years ago
|
||
Likely too late for 70 as well unless we can figure out specific drivers to block.
Jessie, can you help find someone to investigate?
Comment 11•5 years ago
|
||
Alexis, can you write a patch to block 22.19.162.4? Sounds like at least a good interim solution
Updated•5 years ago
|
Assignee | ||
Comment 12•5 years ago
|
||
Driver's Haunted.
Assignee | ||
Comment 13•5 years ago
|
||
PSA: I've never blocklisted a driver before, so not 100% sure if this is right, but this is the basic idea at least.
Comment 14•5 years ago
|
||
Comment 15•5 years ago
|
||
bugherder |
Updated•5 years ago
|
Assignee | ||
Comment 18•5 years ago
|
||
Comment on attachment 9100291 [details]
Bug 1587155 - Block all hardware acceleration for AMD driver 22.19.162.4.
Beta/Release Uplift Approval Request
- User impact if declined: Some users are seeing random nasty visual corruptions on this driver. It goes away if they manually request a driver update, but for whatever reason windows won't automatically do it. We couldn't locally reproduce the issues, so this is the best we can do at the moment.
- Is this code covered by automated tests?: No
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): It blocks a single driver version from using hardware acceleration, so exactly those users will just get a slower version of firefox.
- String changes made/needed:
Comment 19•5 years ago
|
||
Comment on attachment 9100291 [details]
Bug 1587155 - Block all hardware acceleration for AMD driver 22.19.162.4.
Blocks a particular driver, OK for uplift for the RC build.
Comment 20•5 years ago
|
||
bugherder uplift |
Updated•5 years ago
|
Comment 21•5 years ago
|
||
(In reply to Alexis Beingessner [:Gankra] from comment #8)
Hey darkspirit, you were able to reproduce some of the similar issues reported, right? Or were those just A Different But Similar Bug?
(Sorry!) Yes, everything I knew is in bug 1565663. (already in "see also")
Description
•