Annotate on crash reports that content processes are turned on

RESOLVED FIXED in mozilla29

Status

()

RESOLVED FIXED
5 years ago
4 years ago

People

(Reporter: kairo, Assigned: billm)

Tracking

(Blocks: 1 bug)

26 Branch
mozilla29
Points:
---
Dependency tree / graph
Bug Flags:
in-testsuite ?

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

5 years ago
We should annotate on crash reports that e10s is turned on for content processes, so that we can do searches and reports for that.
(Reporter)

Comment 1

5 years ago
And while we're at annotations and e10s, we may want to make sure that bug 616134 is/gets fixed as well.
Blocks: 516752
Depends on: 616134
Blocks: 929045
No longer blocks: 516752
No longer depends on: 616134

Comment 2

5 years ago
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?
Flags: needinfo?(wmccloskey)
Flags: needinfo?(cpeterson)
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
Flags: needinfo?(cpeterson)
Created attachment 8345060 [details] [diff] [review]
crash-annotation
Assignee: nobody → wmccloskey
Status: NEW → ASSIGNED
Attachment #8345060 - Flags: review?(benjamin)
Flags: needinfo?(wmccloskey)

Updated

5 years ago
Attachment #8345060 - Flags: review?(benjamin) → review+
https://hg.mozilla.org/mozilla-central/rev/edc7514508f0
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla29

Updated

5 years ago
Flags: in-testsuite?

Updated

4 years ago
Blocks: 1072278
You need to log in before you can comment on or make changes to this bug.