Mozcrash sorts the content process stack first, even when it's not ideal
Categories
(Testing :: Mozbase, enhancement, P3)
Tracking
(Not tracked)
People
(Reporter: KrisWright, Unassigned)
References
(Blocks 1 open bug)
Details
In bug 1605328 I set MozCrash to sort the content process .dmp file first in a hang report, but sometimes the parent process is more important than the content process, like in bug 1650186. What we need to do to fix this is check if the ipc_channel_error
field in the content process .extra file (if it exists) is ShutdownKill
, and if it isn't, process the uuid-browser.dmp
file first. If we could output the crash signature from the main process in these cases, it would make these crashes a lot clearer.
The point when we parse the .extra file is when we process the dump file and that happens after the files are sorted. So if we want to fix this by changing the sorting order we can either parse the json twice or move the parse step entirely to happen while sorting the dump files and store the whole json dict in the tuple. Alternatively we could deal with this later on while iterating over CrashInfo, and just print from the main process info if it indicates that the information we actually want to see is in there.
![]() |
||
Updated•4 years ago
|
Description
•