Closed
Bug 1029673
Opened 11 years ago
Closed 11 years ago
Correctly report OMTC compositing in crash reports
Categories
(Core :: Graphics, defect)
Tracking
()
RESOLVED
FIXED
mozilla33
People
(Reporter: bjacob, Assigned: bjacob)
Details
Attachments
(1 file)
|
4.01 KB,
patch
|
bas.schouten
:
review+
|
Details | Diff | Splinter Review |
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)
|
||
Updated•11 years ago
|
Attachment #8445309 -
Flags: review?(bas) → review+
|
Assignee | |
Comment 1•11 years ago
|
||
Assignee: nobody → bjacob
|
||
Comment 2•11 years ago
|
||
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla33
You need to log in
before you can comment on or make changes to this bug.
Description
•