Correctly report OMTC compositing in crash reports

RESOLVED FIXED in mozilla33

Status

()

RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: bjacob, Assigned: bjacob)

Tracking

Other Branch
mozilla33
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

Created attachment 8445309 [details] [diff] [review]
gfx-reporter

We have this ScopedGfxFeatureReporter which is how we annotate crash reports with information about what gfx paths were taken, and is in particular what I parse for http://people.mozilla.org/~bjacob/gfx_features_stats/. These haven't been updated in a while, and in particular need to be updated for D3D OMTC compositing. Moreover, it seems that the existing reporting for GL OMTC compositing incorrectly always reports force-enabled (that bool force parameter should reflect whether the feature was force-enabled). Fixing that too.
Attachment #8445309 - Flags: review?(bas)
Attachment #8445309 - Flags: review?(bas) → review+
https://hg.mozilla.org/mozilla-central/rev/6c7eaa0fa407
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla33
You need to log in before you can comment on or make changes to this bug.