Rendering artifacts on every page
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
People
(Reporter: jacobaferrero, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: correctness)
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:89.0) Gecko/20100101 Firefox/89.0
Steps to reproduce:
I'm experiencing flickering and rendering artifacts. Hard to pinpoint where and when they happen exactly, but I've attached a screenshot of them on the new tab screen.
Actual results:
Visual glitches and flickering
Expected results:
No rendering bugs
Comment 1•4 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Graphics: WebRender' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Comment 2•4 years ago
|
||
Thanks for the report! Please open about:support, click on "Copy text to clipboard" and paste it here.
Reporter | ||
Comment 3•4 years ago
|
||
Comment 4•4 years ago
|
||
"gfx.blacklist.webrender.failureid": "FEATURE_FAILURE_GLXTEST_FAILED",
"layers.acceleration.disabled": true,
"windowLayerManagerType": "WebRender (Software)",
"message": "Hardware compositing is disabled"
Right now you are using software rendering. Does this bug occur with hardware rendering or with software rendering?
(Did you disable hardware rendering to fix the bug or does this bug occur with current configuration?)
If this bug occurs with current configuration (software rendering), can it be fixed by setting gfx.webrender.all to true (force-enabling hardware rendering) and restarting FIrefox?
Please also check if this bug still occurs with https://nightly.mozilla.org and also attach its about:support. Thanks!
Reporter | ||
Comment 5•4 years ago
|
||
Setting gfx.webrender.all to true and restarting did not seem to fix it completely (maybe slightly better?) I will try the nightly when I get a chance
Reporter | ||
Comment 6•4 years ago
|
||
The bug also happens on the Nightly from today
Comment 7•4 years ago
|
||
Please try to find a regression range, if possible. At the end you should get a pushlog URL:
$ pip3 install --user mozregression
You can test software rendering with
$ mozregression --good 2021-02-01 --bad 2021-07-01 --pref gfx.webrender.software:true
and hardware rendering with
$ mozregression --good 2021-02-01 --bad 2021-07-01 --pref gfx.webrender.all:true
Reporter | ||
Comment 8•4 years ago
|
||
So with --pref gfx.webrender.all:true it said:
it said 12:45.85 ERROR: Build was expected to be bad! The initial good/bad range seems incorrect.
After I said it was good twice. Same is true for --pref gfx.webrender.all:true. I can't seem to get it to jitter when launched with this tool.
Comment 9•4 years ago
|
||
Would this work?
$ mozregression --find-fix --bad 89 --good 2021-07-01 --pref gfx.webrender.software:true
or
$ mozregression --find-fix --bad 89 --good 2021-07-01 --pref gfx.webrender.all:true
Reporter | ||
Comment 10•4 years ago
|
||
(In reply to Darkspirit from comment #9)
Would this work?
$ mozregression --find-fix --bad 89 --good 2021-07-01 --pref gfx.webrender.software:true
or
$ mozregression --find-fix --bad 89 --good 2021-07-01 --pref gfx.webrender.all:true
Yup no problems with these.
Comment 11•4 years ago
|
||
"numTotalWindows": 4,
"numAcceleratedWindows": 4,
"windowLayerManagerType": "WebRender (Software)",
It could be that the bug only occurs with multiple windows or if you do other specific steps.
"webgl.dxgl.enabled": true,
"webgl.enable-ahardwarebuffer": true,
These prefs are for Windows and Android. Please set them back to false (default). Such prefs could also be the cause for bugs.
Reporter | ||
Comment 12•4 years ago
|
||
Okay, so I tried to reproduce the situation in my main FF, and it only starts happening after I install the ImTranslator extension (https://addons.mozilla.org/en-US/firefox/addon/imtranslator).
Comment 13•3 years ago
|
||
(In reply to jacobaferrero from comment #0)
Does this problem still occur?
Reporter | ||
Comment 14•3 years ago
|
||
Yes, still happening. I really have no idea what is causing it.
Updated•3 years ago
|
Updated•3 years ago
|
Comment 15•3 years ago
|
||
The bug has a release status flag that shows some version of Firefox is affected, thus it will be considered confirmed.
Comment 16•1 year ago
|
||
Hi, does the issue still happen for you? Thanks!
Reporter | ||
Comment 17•1 year ago
|
||
Hi, no I haven't seen this happening anymore for a while.
Comment 18•1 year ago
|
||
(In reply to jacobaferrero from comment #17)
Hi, no I haven't seen this happening anymore for a while.
Thanks for the quick reply!
Description
•