Closed
Bug 929012
Opened 11 years ago
Closed 11 years ago
Annotate on crash reports that content processes are turned on
Categories
(Core :: IPC, defect)
Tracking
()
RESOLVED
FIXED
mozilla29
People
(Reporter: kairo, Assigned: billm)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
1.08 KB,
patch
|
benjamin
:
review+
|
Details | Diff | Splinter Review |
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•11 years ago
|
||
And while we're at annotations and e10s, we may want to make sure that bug 616134 is/gets fixed as well.
Updated•11 years ago
|
Updated•11 years ago
|
Comment 2•11 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)
Comment 3•11 years ago
|
||
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)
Assignee | ||
Comment 4•11 years ago
|
||
Assignee: nobody → wmccloskey
Status: NEW → ASSIGNED
Attachment #8345060 -
Flags: review?(benjamin)
Flags: needinfo?(wmccloskey)
Updated•11 years ago
|
Attachment #8345060 -
Flags: review?(benjamin) → review+
Assignee | ||
Comment 5•11 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla29
Updated•11 years ago
|
Flags: in-testsuite?
You need to log in
before you can comment on or make changes to this bug.
Description
•