Closed Bug 1072278 Opened 10 years ago Closed 10 years ago

Annotate crash reports with e10s information

Categories

(Core :: General, defect)

x86_64
All
defect
Not set
normal

Tracking

()

RESOLVED INVALID
Tracking Status
e10s ? ---

People

(Reporter: jimm, Unassigned)

References

Details

Bug 929012 added annotations tied to browser.tabs.remote, but afaict, that pref isn't set or needed when we enable autostart e10s. In my profile browser.tabs.remote is false and e10s still works. The new Options checkbox doesn't set it either. 

Looking at some e10s related crash reports in bug 1065042, I don't see 'DOMIPCEnabled'.
I see that annotation on all crashes that have e10s enabled. Can you point me to a specific one where you are sure e10s is enabled but the annotation is missing?
(In reply to Robert Kaiser (:kairo@mozilla.com) from comment #1)
> I see that annotation on all crashes that have e10s enabled. Can you point
> me to a specific one where you are sure e10s is enabled but the annotation
> is missing?

https://crash-stats.mozilla.com/report/index/cc960924-4e5e-4fcb-81fa-9b8f72140807

Maybe it only shows up in the parent process?
The annotation is set in a different place nowadays:
http://mxr.mozilla.org/mozilla-central/source/docshell/base/nsDocShell.cpp#2295
We had to change it to deal with "Open new e10s window".

It was intended to be set only in the parent process. We can already detect child process crashes because they're marked as "Process type" = content.

For ease of querying, it might make sense to set the annotation in the child, too. That would be very easy.
I've actually seen the annotation in child processes, even though as you say it's somewhat redundant.
Ok, if we're sure this is getting sent and that patch I was looking at is out dates, I guess we can close this. Thanks for the clarification.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.