Closed Bug 1245165 Opened 8 years ago Closed 8 years ago

No plugin name and version annotations on plugin crashes with e10s turned on

Categories

(Core Graveyard :: Plug-ins, defect)

defect
Not set
normal

Tracking

(e10sm9+)

RESOLVED FIXED
Tracking Status
e10s m9+ ---

People

(Reporter: kairo, Assigned: jimm)

References

Details

Agree this is pretty important.

These annotations are written here: http://hg.mozilla.org/mozilla-central/annotate/5f9ba76eb3b1/dom/plugins/ipc/PluginModuleParent.cpp#l836

I'd expect PluginModuleChromeParent::WriteExtraDataForMinidump to be the codepath for both chrome and plugin crashes. Bill am I wrong about that class being used (in the chrome process) in the e10s case?
Flags: needinfo?(wmccloskey)
something wee need for crash analysis.
Assignee: nobody → wmccloskey
Flags: needinfo?(wmccloskey)
Assignee: wmccloskey → jmathies
I just tested this in a local mc build and the annotations are getting set properly.

https://crash-stats.mozilla.com/report/index/a009eb6d-01e9-4743-b82a-41fe42160317
I knew this code looked familiar! Fixed by bug 1256943.

http://hg.mozilla.org/mozilla-central/rev/3c8ea88e6916
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.