Most crashes occur on the main thread. So when a crash does occur on another thread, it is often interesting to developers (e.g. https://crash-stats.mozilla.com/report/index/80c775c3-cc38-403b-9f90-70aa82120621). So in the webapp when viewing an individual report, I'd like to gently highlight the fact that the crash is on a thread other than thread 0. For instance, right after the text "Crashing Thread", add in "(Thread 22)" in italics.
Note that on Android the Gecko thread is never Thread 0, FWIW.
Let's wait for JSON MDSW
Depends on: 906131
This is pretty trivial to implement now for bsmedberg's comment 0: we know the crashing thread number, we can simply compare it to 0. It's a little harder to make it useful for Android crashes, but I don't know that we need to solve that for a first pass.
The thread number is now included in the headings, including the "Crashing Thread (0)" heading, which covers the request in comment 0.
Status: NEW → RESOLVED
Last Resolved: 2 months ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.