Open Bug 1289671 Opened 6 years ago Updated 2 months ago

[meta] [Uptime] Crash report submission

Categories

(Firefox :: General, defect, P3)

defect

Tracking

()

People

(Reporter: n.nethercote, Unassigned)

References

(Depends on 2 open bugs)

Details

(Keywords: meta, Whiteboard: [Uptime])

This is a Project Uptime meta-bug for bugs aimed at increasing the crash submission rate.
Blocks: 1289677
njn, just to understand what the baseline for this effort is - what is the current % of crash reports submitted after prompt?
Flags: needinfo?(n.nethercote)
I don't know. I think bsmedberg knows these numbers -- the rates vary significantly for different kinds of crashes.
Flags: needinfo?(n.nethercote) → needinfo?(benjamin)
If we're resource-constrained, I don't think we should focus on this
Flags: needinfo?(benjamin)
Priority: -- → P2
While prioritization of this would be an interesting discussion, I just wanted to understand if we have any data at all: > What is the current % of crash reports submitted after prompt?
Flags: needinfo?(benjamin)
Sorry wasn't done. I think we should focus primarily on client stackwalking so that we don't have to ask users in general to submit crashes. We can still prompt when we need additional data, and even be more aggressive about it because it's less frequent.

That said, the way to compute submission rates is to compare the PROCESS_CRASH_SUBMIT_ATTEMPT histogram with the relevant "crashes detected" number. So for each type:

main process: PROCESS_CRASH_SUBMIT_ATTEMPT['main-crash'] / COUNT(crash pings)
content process: PROCESS_CRASH_SUBMIT_ATTEMPT['content-crash'] / SUBPROCESS_CRASHES_WITH_DUMP['content']
npapi and gmp: PROCESS_CRASH_SUBMIT_ATTEMPT['plugin-crash'+'plugin-hang'] / SUBPROCESS_CRASHES_WITH_DUMP['plugin'+'pluginhang'+'gmplugin']

I don't have a parquet dataset for this because we currently don't aggregate the submit-attempt or submit-success numbers. Here's an email from data I analyzed a while back, though:

> Main crashes are typically submitted at a rate of around 50% (slightly more on nightly; slightly less on release).
> 
> Content crashes are typically submitted at a rate between 10-15%, but the rate is more variable. It sometimes dips down to 5% and occasionally up to 20%. Here are some hunches for why this may be more variable:
> 
>     I believe (with some evidence) that people are more likely to submit new crashes, and less likely to submit crashes that they've already submitted.
>     I also expect (with little evidence) that a crash that happens when a tab or window is closed are much less likely to be submitted than crashes that happen while a page is active.
> 
> Plugin crashes are submitted at a rate between 0.5% and 0.75%.
Priority: P2 → P3
(In reply to Benjamin Smedberg [:bsmedberg] from comment #5)
> I think we should focus primarily on client stackwalking
> so that we don't have to ask users in general to submit crashes. We can
> still prompt when we need additional data, and even be more aggressive about
> it because it's less frequent.

FWIW, this bug covers anything that might increase the crash submission rate, including the client-side stack walking work (which is among the blocking bugs).
Flags: needinfo?(benjamin)
Depends on: 1287178
Depends on: 1333125

Mass-removing myself from cc; search for 12b9dfe4-ece3-40dc-8d23-60e179f64ac1 or any reasonable part thereof, to mass-delete these notifications (and sorry!)

Summary: [Uptime] Crash report submission → [meta] [Uptime] Crash report submission
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.