Closed
Bug 1277664
Opened 9 years ago
Closed 9 years ago
Whitelist IPCMessageName and IPCMessageSize fields to be public in Metadata tab
Categories
(Socorro :: General, task)
Socorro
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mccr8, Unassigned)
References
Details
Similar to bug 1260270, I'd like these two fields to be public and searchable, so I can, say, get a breakdown of what the IPCMessageNames are that are causing the assertions in bug 1271102.
IPCMessageName is an internally generated C++ name so it shouldn't cause a problem to make public, and the message size is kind of like the OOM allocation size, in that it is just the size of a particular large allocation.
Here is an example crash report:
https://crash-stats.mozilla.com/report/index/1fcb692a-41fb-4ac4-afb5-99fcd2160602
Comment 1•9 years ago
|
||
Both fields added as `ipc_message_name` and `ipc_message_size`. Here's an example: https://crash-stats.mozilla.com/search/?product=Firefox&ipc_message_name=%21__null__&_facets=ipc_message_size&_facets=ipc_message_name&_columns=ipc_message_size&_columns=ipc_message_name#crash-reports
Note that since I had to change the mapping of ipc_message_name, it will only work with data coming in starting next Monday, when a new Elasticsearch index is created.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 2•9 years ago
|
||
Thanks!
You need to log in
before you can comment on or make changes to this bug.
Description
•