Closed Bug 687115 Opened 13 years ago Closed 7 years ago

[tracking] Reports on devices per signature and crashes per device

Categories

(Socorro :: General, task)

x86
All
task
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: chofmann, Unassigned)

References

Details

(Keywords: meta)

naoki mentioned that he occationally spots crashes that are device specific when plowing through the mobile data.

we should build a report that helps to do this and also give us a sense of which of the android devices seems to be the crashiest and also attempt to correlate that with the popularity of devices.

Here is a sample of the kind of report that might be possible, using 1 days worth of data from the .csv files.

First section of the report might show crash counts by device like:

count -- device

2419 \N
 151 motorola MB860 
 100 asus Transformer TF101 
  63 Motorola Xoom 
  46 motorola DROIDX 
  42 samsung GT-P1000 
  39 samsung GT-I9100 
  33 Acer A500 
  25 samsung GT-I9000 
  19 LGE LG-P999 
  18 Acer A501 
  16 samsung GT-P7100 
  15 motorola MZ601 
  13 motorola DROID X2 
  13 lge LG-P990 
  12 HTC HTC Desire 
  11 motorola MZ605 
  10 samsung SC-02C 
  10 samsung Nexus S 
  10 Motorola MZ604 
  10 HTC HTC Glacier 
+ more

Second section of the report might drill down in a second pass to show a top crash list of signatures for that device with information about variance from the overall top crash count.

motorola MB860
  67 libc.so@0x15f5e
  56 libc.so@0xae16
  25 libc.so@0x1209c
   1 libdvm.so@0x41910
   1 libc.so@0xf3c0
   1 libc.so@0x13b00

asus Transformer TF101
  96 _moz_cairo_surface_get_device_offset
   1 libjnigraphics.so@0x6ee
   1 libc.so@0x15c1c
   1 libc.so@0x13370
   1 libc.so@0x132a2

Motorola Xoom
  63 _moz_cairo_surface_get_device_offset

motorola DROIDX
  33 libc.so@0x12c6e
   3 libc.so@0xb45c
   2 libc.so@0x12cdc
   2 @0x71a7f7a8
   1 nsDocShell::RefreshURI
   1 mozilla::scache::StartupCache::WaitOnWriteThread
   1 libdvm.so@0x40438
   1 libc.so@0x12c4e
   1 gfxTextRun::GlyphRunIterator::NextRun
   1 @0xafd0b45c

or we could integrate this kind of analysis into the top crash list by showing the list of "found on devices"  similar to the way that we show "found in releases".
Component: Socorro → General
Product: Webtools → Socorro
I'm running such reports right now, with both section implemented. See the "Device Crash Report" entries on https://crash-analysis.mozilla.com/rkaiser/0000.overview.html

For Socorro, we really want this as two different things, though, and therefore this bug is problematic, as the two things will have different implementation schedules.

"First section" from comment #0 should be a new report of some kind, or a query option (the latter probably makes more sense, it's another "top crashes by signature filtered by some criteria" report, and IMHO, that makes most sense in search).

"Second section" from comment #0 should be implemented as an entry in the Signature Summary.


I'll file bugs on those two parts and make this a tracking bug for them.
Keywords: meta
Summary: socorro report to show mobile crashes by device → [tracking] Reports on devices per signature and crashes per device
Depends on: 853452
Depends on: 853455
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.