1299964 - Content process crash is categorized as browser crash

Status: RESOLVED DUPLICATE of bug 1277582

(Toolkit :: Crash Reporting, defect)

Description

[Bill McCloskey [inactive unless it's an emergency] (:billm)]

Here's an example crash:
https://crash-stats.mozilla.com/report/index/02bf3b66-c860-46eb-b9e6-deb3d2160901

Notice that the stack starts with content_process_main. But there's no ProcessType=content metadata. I'm not sure how this is happening.

All the crashes with this signature look like this. The signature shows up under browser crashes in crash-stats, as one would expect. So this is causing our crash numbers to look worse in some sense since browser crashes are worse than content process crashes.

Comment 1

[Gabriele Svelto [:gsvelto]]

Smells like the same issue we've seem in bug 1282776. The ProcessType field is written together with other metadata in CrashReporterParent::GenerateChildData() at the end of the crash reporting process. 

http://hg.mozilla.org/mozilla-central/file/60b340e55efe/dom/ipc/CrashReporterParent.cpp#l115

Somehow sometimes all that metadata is missing which indicates that either the method wasn't called, or it was called but failed. Unfortunately I could never reproduce the issue so it's hard to tell what might be causing it to fail.

Comment 2

[Bill McCloskey [inactive unless it's an emergency] (:billm)]

I think I figured out what's happening here. See https://bugzilla.mozilla.org/show_bug.cgi?id=1277582#c66.

Comment 3

[Gabriele Svelto [:gsvelto]]

(In reply to Bill McCloskey (:billm) from comment #2)
> I think I figured out what's happening here. See
> https://bugzilla.mozilla.org/show_bug.cgi?id=1277582#c66.

Hah, nice catch!