Closed Bug 1187453 Opened 5 years ago Closed 5 years ago

Fix some gfx reporting holes

Categories

(Toolkit :: Telemetry, defect)

defect
Not set

Tracking

()

RESOLVED FIXED
mozilla42
Tracking Status
firefox42 --- fixed

People

(Reporter: dvander, Assigned: dvander)

References

Details

Attachments

(3 files)

We need a few more bits and bobs to explain some of the data we're seeing in gfx telemetry. A large number of users have no compositor but have d3d11 available, and we want to know whether OMTC has been explicitly disabled on those systems.

Second, a small percentage of users have WARP, and I'd like to know whether that's due to device failures or blacklists.

Finally, it looks like sometimes Windows can report a monitor refresh rate of "1". This appears to be some kind of error case and I'd like to clarify that in the docs.
To distinguish between whether or not WARP was chosen for blacklisting versus D3D11CreateDevice() failing.
Attachment #8638728 - Flags: review?(matt.woodrow)
Attachment #8638728 - Flags: review?(matt.woodrow) → review+
Attachment #8638726 - Flags: review?(vdjeric) → review+
Attachment #8638730 - Flags: review?(vdjeric) → review+
You need to log in before you can comment on or make changes to this bug.