Rod Pemberton
2021-06-04 01:23:19 UTC
<OT>
OMG! Mozilla enabled their broken rendering engine for Firefox 89.0.
I know this is off-topic, but some of you may be using the Firefox
browser and have this issue now.
Go to MotionMark link below and run their v1.1 benchmark. Your result
should **NOT** be a low number, like below 10. This takes a few
minutes to run.
https://browserbench.org/MotionMark1.1/
If you get a low number, you'll need to go to https://about:config, and
toggle this Firefox setting to true:
gfx.webrender.force-disabled
Also, make sure that these Firefox settings are still set to false:
gfx.webrender.all
gfx.webrender.enabled
There will be other gfx.webrender.* settings that are now set to true
by default for Firefox 89.0. You can try toggling them one-by-one and
checking the benchmark, if you don't want to fully disable Webrender
with the force disable setting. I'll attempt this at a later time.
E.g., MotionMark1.1 results for my 2009 components computer:
89.0 74+ without Webrender - 100% correctly rendered
89.0 4.33 with Webrender - ~70% correctly rendered
88.0.1 72+ without Webrender - 100% correctly rendered
88.0.1 1.08 with Webrender - ~30% correctly rendered
As you can see, they've improved Webrender from 88.0.1 to 89.0, but it's
still not rendering MotionMark's benchmark correctly or completely.
Webrender is really slow too. The most noticeable rendering which is
still broken is of the circles with lines moving in out about their
radius, as all the lines are missing ...
So, if you've got an older machine, like I do, or if their Webrender is
just broken ... (which it very likely is), you may want to try out the
browser setting changes above.
OMG! Mozilla enabled their broken rendering engine for Firefox 89.0.
I know this is off-topic, but some of you may be using the Firefox
browser and have this issue now.
Go to MotionMark link below and run their v1.1 benchmark. Your result
should **NOT** be a low number, like below 10. This takes a few
minutes to run.
https://browserbench.org/MotionMark1.1/
If you get a low number, you'll need to go to https://about:config, and
toggle this Firefox setting to true:
gfx.webrender.force-disabled
Also, make sure that these Firefox settings are still set to false:
gfx.webrender.all
gfx.webrender.enabled
There will be other gfx.webrender.* settings that are now set to true
by default for Firefox 89.0. You can try toggling them one-by-one and
checking the benchmark, if you don't want to fully disable Webrender
with the force disable setting. I'll attempt this at a later time.
E.g., MotionMark1.1 results for my 2009 components computer:
89.0 74+ without Webrender - 100% correctly rendered
89.0 4.33 with Webrender - ~70% correctly rendered
88.0.1 72+ without Webrender - 100% correctly rendered
88.0.1 1.08 with Webrender - ~30% correctly rendered
As you can see, they've improved Webrender from 88.0.1 to 89.0, but it's
still not rendering MotionMark's benchmark correctly or completely.
Webrender is really slow too. The most noticeable rendering which is
still broken is of the circles with lines moving in out about their
radius, as all the lines are missing ...
So, if you've got an older machine, like I do, or if their Webrender is
just broken ... (which it very likely is), you may want to try out the
browser setting changes above.
--
Let's ask the radical leftists something. After Joe Biden's sick
sexual comment about a really young girl, does PizzaGate live?
Let's ask the radical leftists something. After Joe Biden's sick
sexual comment about a really young girl, does PizzaGate live?