Visual corruption with WR in logged in old reddit
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox81 | --- | affected |
People
(Reporter: yoasif, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
See screenshot.
Page is https://www.reddit.com/message/comments/
wr-capture: https://drive.google.com/file/d/19hSvzAjxJO10EOFb3Wo0CMd_EmnF_cw-/view?usp=sharing
Reporter | ||
Comment 1•4 years ago
|
||
Comment 2•4 years ago
|
||
Hmm, I could not reproduce the problem with my Win10 PCs.
Asif Youssuff, can you reproduce the problem with other Win10 PC?
Reporter | ||
Comment 3•4 years ago
|
||
Sotaro, I don't use any other Windows PC with enough regularity to try to reproduce the issue.
Updated•4 years ago
|
Comment 4•4 years ago
|
||
:gw, do you have any ideas about a cause of the problem?
Comment 5•4 years ago
|
||
I also can't repro locally on my Win10/Intel machine. Does it still occur if DirectComposition is disabled in about:config?
Reporter | ||
Comment 6•4 years ago
|
||
What is the preference for DirectComposition in about:config?
Comment 7•4 years ago
|
||
(In reply to Asif Youssuff from comment #6)
What is the preference for DirectComposition in about:config?
Setting gfx.webrender.compositor
to be false and restarting should do it, I think.
Reporter | ||
Updated•4 years ago
|
Comment 8•4 years ago
|
||
@Asif: Could you also try updating the intel graphics driver?
Updated•4 years ago
|
Updated•4 years ago
|
Reporter | ||
Comment 9•4 years ago
|
||
I haven't seen the issue in the days since disabling DirectComposition.
I'm pretty sure I was running the latest version of the driver provided by Windows Update - I have now downloaded a newer version via Intel's website.
I went ahead and re-enabled DirectComposition since updating the driver this morning.
Comment 10•4 years ago
|
||
Asif, did the new driver version solve the problem with DirectComposition enabled? Thanks!
Reporter | ||
Comment 11•4 years ago
|
||
Andrew, I honestly stopped running Windows on that machine due to the awful performance on it - and it didn't happen all the time, so I'd probably have to run it for a somewhat extended period of time. I'll go ahead and do that now since I have another needinfo for that same hardware.
Reporter | ||
Comment 12•4 years ago
|
||
(In reply to Andrew Osmond [:aosmond] from comment #10)
Asif, did the new driver version solve the problem with DirectComposition enabled? Thanks!
It looks like the new driver version fixed the issue.
Updated•4 years ago
|
Reporter | ||
Comment 13•4 years ago
|
||
Kris, isn't this still a bug with the driver version I initially reported the bug with?
Comment 14•4 years ago
|
||
@andrew: Asif has a point, should we block the driver version?
Updated•4 years ago
|
Updated•3 years ago
|
Updated•7 months ago
|
Description
•