Block WebRender on the GT218 (GeForce 210/205/310 etc.)

VERIFIED FIXED in Firefox 64



5 months ago
4 months ago


(Reporter: jrmuizel, Assigned: kats)


(Blocks: 1 bug)

Dependency tree / graph

Firefox Tracking Flags

(firefox64+ verified, firefox65 verified)



(1 attachment)



5 months ago
These are very under powered GPUs. See:

WebRender doesn't work well enough on them yet to consider shipping. See bug 1501378.

For now, we'll block them on 64 and reconsider once we have picture caching.

Here's a list of GT218 device id's:

            "GT218": [
            "GT218M": [
            "GT218GL": [
            "GT218GLM": [


5 months ago
Blocks: 1386669
Priority: -- → P1

Comment 1

5 months ago
GT218 is used in cards like the GeForce 210, GeForce 205, GeForce 310, some GeForce 405s etc.


5 months ago
Summary: Block WebRender on the GT218 → Block WebRender on the GT218 (GeForce 210/205/310 etc.)
I'll write a patch.
Assignee: nobody → kats
Since bug 1498417 touches the same code I'm fixing up the patch on that and doing it together with this one.

Try push with both patches (not that try will really catch much in the way of functional errors for this...):
Depends on: 1498417

Comment 5

5 months ago
Pushed by
Block a bunch of low-powered nvidia cards from getting WebRender. r=mattwoodrow

Comment 6

5 months ago
Last Resolved: 5 months ago
status-firefox65: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla65

Comment 7

4 months ago
[Tracking Requested - why for this release]: We're considering doing a limited release of WebRender on 64. It would be really good to have this additional blocking there.
tracking-firefox64: --- → ?

Comment 8

4 months ago
Comment on attachment 9019766 [details]
Bug 1501533 - Block a bunch of low-powered nvidia cards from getting WebRender. r?mattwoodrow

[Beta/Release Uplift Approval Request]

Feature/Bug causing the regression: None

User impact if declined: Users with low-powered nvidia cards will have WebRender enabled and it's not a very good experience there

Is this code covered by automated tests?: No

Has the fix been verified in Nightly?: Yes

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): This is very low risk changes as it just adds some additional blocking of the WebRender feature.

String changes made/needed:
Attachment #9019766 - Flags: approval-mozilla-beta?
Hoping to gtb 64 rc2 today or tomorrow.
status-firefox64: --- → affected
tracking-firefox64: ? → +
Attachment #9019766 - Flags: approval-mozilla-beta? → approval-mozilla-release?
Comment on attachment 9019766 [details]
Bug 1501533 - Block a bunch of low-powered nvidia cards from getting WebRender. r?mattwoodrow

blacklisting some devices for webrender, approved for 64.0 rc2
Attachment #9019766 - Flags: approval-mozilla-release? → approval-mozilla-release+

Comment 11

4 months ago
Hi Jeff, how can we test this issue ? does this mean that We should not see WebRender on Windows 10 with Nvidia GeForce 210, even if we manually set the gfx.webrender.all in about:config ?

What are the steps to verify this issue ?
Flags: qe-verify+
Flags: needinfo?(jmuizelaar)


4 months ago
Flags: needinfo?(kats)
The pref to modify is gfx.webrender.all.qualified - and yes, if you have a GeForce 210 card on a desktop Windows 10 machine, then without this patch you should get WR enabled in about:support, and with this patch it should be disabled.
Flags: needinfo?(kats)
Flags: needinfo?(jmuizelaar)

Comment 13

4 months ago
status-firefox64: affected → fixed

Comment 14

4 months ago
Hi, I can confirm this issue as FIXED in firefox BETA 65.0b2 and Nightly 65.0a1 (2018-12-10)on a WINDOWS 10 with an Nvidia GeForce 210, after setting the gfx.webrender.all.qualified to true in about config , the WebRender is no longer recognized and displayed in about:support. I will mark this issue accordingly.
status-firefox64: fixed → verified
status-firefox65: fixed → verified
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.