Closed
Bug 894995
Opened 11 years ago
Closed 11 years ago
"Process type" no longer being reported by Socorro
Categories
(Socorro :: Webapp, task)
Socorro
Webapp
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: smichaud, Assigned: peterbe)
References
Details
This field can contain very valuable information -- for example the actual plugin name and version in crashes that happen in a plugin child process. Socorro used to report this information. For example see bug 852232 comment #0, which copies information available for bp-a906c7b4-1e5e-4def-95a3-f10be2130318 as of 2013-03-18. But when you visit https://crash-stats.mozilla.com/report/index/a906c7b4-1e5e-4def-95a3-f10be2130318 now, you don't see this information. As best I can tell, this information started being included in Socorro reports as of bug 711224.
Reporter | ||
Comment 1•11 years ago
|
||
Scoobidiver, Ted, do you know anything about this? And there's another problem, which I haven't yet reported because I don't yet have enough information: I remember that, when Firefox got terminated because of an OS-level assertion or uncaught Objective-C exception, Socorro reports contained information about, for example, what kind of assertion/exception had happened. But I can't remember which field (in the Socorro report) contained this information. Do I remember correctly, and this information also disappeared from recent Socorro reports?
Comment 2•11 years ago
|
||
This looks like a regression from the switchover to the new webapp. The old PHP app is still online (for now), and you can compare its output here: https://crash-stats-php.mozilla.org/report/index/a906c7b4-1e5e-4def-95a3-f10be2130318 (you'll have to click through the SSL cert error).
Comment 3•11 years ago
|
||
Yes, this looks like a regression, and potentially another blocker for turning off PHP.
Component: General → Webapp
Reporter | ||
Comment 4•11 years ago
|
||
> I remember that, when Firefox got terminated because of an OS-level
> assertion or uncaught Objective-C exception, Socorro reports
> contained information about, for example, what kind of
> assertion/exception had happened. But I can't remember which field
> (in the Socorro report) contained this information.
Do I remember right about this?
Comment 5•11 years ago
|
||
Commits pushed to master at https://github.com/mozilla/socorro-crashstats https://github.com/mozilla/socorro-crashstats/commit/6a23814984334117f29d834c615fd716cca5a389 fixes bug 894995 - "Process type" no longer being reported by Socorro https://github.com/mozilla/socorro-crashstats/commit/52c26404274bb687a0b3a5c3640fd454270f214e Merge pull request #433 from peterbe/bug-894995-process-type-no-longer-being-reported-by-socorro fixes bug 894995 - "Process type" no longer being reported by Socorro
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Assignee: nobody → peterbe
Assignee | ||
Comment 7•11 years ago
|
||
An example http://crash-stats-dev.allizom.org/report/index/2b69c456-cb76-45a9-8845-354592130717
Reporter | ||
Comment 8•11 years ago
|
||
Never mind. I found this: https://hg.mozilla.org/mozilla-central/annotate/604c8518cc50/xpcom/base/nsObjCExceptions.h#l43 So we apparently still do append exception information to Breakpad/Socorro reports, to the App Notes field -- which *is* still displayed by the Socorro WebApp.
Flags: needinfo?(ted)
Flags: needinfo?(scoobidiver)
Reporter | ||
Comment 9•11 years ago
|
||
By the way, thanks very much for the quick fix!
You need to log in
before you can comment on or make changes to this bug.
Description
•