Bug 1664843 Comment 25 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

I've been comparing a bad build and a good build. It looks like the telemetry gfx environment is the exact same, and matches [the one from this crash report](https://crash-stats.mozilla.org/report/index/ea8d92b8-3f3e-4e0e-8188-4a6840200914#tab-telemetryenvironment). This machine only has a single GPU.

However, the information displayed on https://webglreport.com/ has a lot of differences! For example:

|  | Bad build | Good build |
|--|--|--|
| Max Varying Vectors | 32 | 15 |
| Max Combined Texture Image Units | 48 | 16 |
| Aliased Line Width Range | [1, 7] | [1, 1] |
| Advertises support for the EXT_float_blend | Yes | No |

I wonder if there's some code in Firefox that would be limiting those queryable numbers to something smaller, and if the different way of querying GPUs broke it.
I've been comparing a bad build and a good build. It looks like the telemetry gfx environment is the exact same, and matches [the one from this crash report](https://crash-stats.mozilla.org/report/index/ea8d92b8-3f3e-4e0e-8188-4a6840200914#tab-telemetryenvironment). This machine only has a single GPU.

However, the information displayed on https://webglreport.com/ has a lot of differences! For example:

|  | [Bad build](https://archive.mozilla.org/pub/firefox/nightly/2020/09/2020-09-28-09-48-30-mozilla-central/firefox-83.0a1.en-US.mac.dmg) | [Good build](https://archive.mozilla.org/pub/firefox/nightly/2020/09/2020-09-28-21-28-24-mozilla-central/firefox-83.0a1.en-US.mac.dmg) |
|--|--|--|
| Max Varying Vectors | 32 | 15 |
| Max Combined Texture Image Units | 48 | 16 |
| Aliased Line Width Range | [1, 7] | [1, 1] |
| Advertises support for the EXT_float_blend | Yes | No |

I wonder if there's some code in Firefox that would be limiting those queryable numbers to something smaller, and if the different way of querying GPUs broke it.
I've been comparing a bad build and a good build. It looks like the telemetry gfx environment is the exact same, and matches [the one from this crash report](https://crash-stats.mozilla.org/report/index/ea8d92b8-3f3e-4e0e-8188-4a6840200914#tab-telemetryenvironment). This machine only has a single GPU.

However, the information displayed on https://webglreport.com/ has a lot of differences! For example:

|  | [Bad build](https://archive.mozilla.org/pub/firefox/nightly/2020/09/2020-09-28-09-48-30-mozilla-central/firefox-83.0a1.en-US.mac.dmg) | [Good build](https://archive.mozilla.org/pub/firefox/nightly/2020/09/2020-09-28-21-28-24-mozilla-central/firefox-83.0a1.en-US.mac.dmg) |
|--|--|--|
| Max Varying Vectors | 32 | 15 |
| Max Combined Texture Image Units | 48 | 16 |
| Aliased Line Width Range | [1, 7] | [1, 1] |
| Advertises support for EXT_float_blend | Yes | No |

I wonder if there's some code in Firefox that would be limiting those queryable numbers to something smaller, and if the different way of querying GPUs broke it.

Back to Bug 1664843 Comment 25