We should annotate on crash reports that e10s is turned on for content processes, so that we can do searches and reports for that.
And while we're at annotations and e10s, we may want to make sure that bug 616134 is/gets fixed as well.
bill/cpeterson: now that the blog post has gotten a lot of press and people are actively trying e10s mode on nightly this is significantly skewing crash-stats. Can you prioritize getting this annotation into nightly so that we can separate out the e10s crashes from normal nightly stats?
On IRC, bsmedberg said we need to add a DOMIPCEnabled=1 annotation using nsICrashReporter.annotateCrashReport(). Here is an example: https://mxr.mozilla.org/mozilla-central/source/accessible/src/base/nsAccessibilityService.cpp#1100
Created attachment 8345060 [details] [diff] [review] crash-annotation
Assignee: nobody → wmccloskey
Status: NEW → ASSIGNED
Attachment #8345060 - Flags: review?(benjamin)
5 years ago
Depends on: 948238
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla29
You need to log in before you can comment on or make changes to this bug.