Show crash rate for e10s main and content processes, over time

RESOLVED WONTFIX

Status

Socorro
General
P2
enhancement
RESOLVED WONTFIX
3 years ago
4 months ago

People

(Reporter: lizzard, Unassigned)

Tracking

unspecified

Firefox Tracking Flags

(e10s+)

Details

I would like to be able to look at https://crash-stats.mozilla.com/daily?p=Firefox
And see crash rates on the graph, for products with e10s enabled (dom ipc enabled preference on).  It would be especially great if the graph showed different lines plotted for the browser process and the content process.   I think this will help the e10s team, QA, and release management to see a much more clear picture of e10s crash rates.
(Reporter)

Updated

3 years ago
Severity: normal → enhancement
Hey Schalk,

Do you plan on keeping the "Crashes per User" (aka /daily) UI around?
Flags: needinfo?(schalk.neethling.bugs)
(In reply to Liz Henry :lizzard from comment #0)
> I would like to be able to look at
> https://crash-stats.mozilla.com/daily?p=Firefox
> And see crash rates on the graph, for products with e10s enabled (dom ipc
> enabled preference on).  It would be especially great if the graph showed
> different lines plotted for the browser process and the content process.   I
> think this will help the e10s team, QA, and release management to see a much
> more clear picture of e10s crash rates.

Do you know if this is something the client communicates now? Can you link me to an example crash and I can look if not?
Flags: needinfo?(lhenry)
(Reporter)

Comment 3

3 years ago
Sure!  Here is a list of current content process crashes for Firefox 37 with e10s, for example.

https://crash-stats.mozilla.com/search/?product=Firefox&dom_ipc_enabled=!__null__&version=37.0a1&process_type=content&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-signature

vs. a search for browser crashes (the main process):

https://crash-stats.mozilla.com/search/?product=Firefox&dom_ipc_enabled=!__null__&version=37.0a1&process_type=browser&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-signature

In theory we want the crash rates with e10s enabled to be as good as, or better, than the crash rate with it not enabled.  In practice this might mean startup and browser crash rate is more important than most content crashes (since content crashes in multiprocess Firefox are only supposed to crash the tab in which they're loaded, without crashing the entire browser).
Flags: needinfo?(lhenry)
Adrian, do you have any plans to add graphs for supersearch results (or just on top of ES at all, Kibana allows this for example)?

That might be a better use of time than trying to extend that old /daily UI...
Flags: needinfo?(adrian)
Yes, I do! Super Search and Signature Report will be getting graphs on about any field or combination of fields, but that requires us to move to Elasticsearch 1.x first. That could be a goal for next quarter.
Flags: needinfo?(adrian)
(In reply to Robert Helmer [:rhelmer] from comment #1)
> Hey Schalk,
> 
> Do you plan on keeping the "Crashes per User" (aka /daily) UI around?

This is going to be determined once we have better analytics reporting but, from the current data it does not seem that, that get's used a whole lot.
Flags: needinfo?(schalk.neethling.bugs)
It would be nice to track the Flash plugin process crashes over time, too.

However, bsmedberg might be planning to track Flash plugin process crash counts using FHR instead. The FHR data is supposedly more accurate because plugin crash reports are grossly underreported. We believe only ~1% of plugin crashes are actually submitted.
tracking-e10s: --- → +

Comment 8

3 years ago
All we'd need for /daily there is to be able to graph by process type (browser, plugin, content). My long-term graphs already separate out plugin crashes, FWIW, but with the caveats of what Chris says - FHR data should be able to give us much better data on all those numbers, but unfortunately, FHR can't be used for short-time views of recent data due to its mechanism of sending data with much delay at times. Crash-stats data of submitted crashes can give us those views and enable us to react fast, with the downside of being incomplete data (i.e. depending on people to actually submit the crashes).
tracking-e10s: + → ---
Priority: -- → P2
Glob, can you add the e10s flag to this component?
Flags: needinfo?(glob)
(In reply to Brad Lassey [:blassey] (use needinfo?) from comment #9)
> Glob, can you add the e10s flag to this component?

tracking-e10s added to Socorro :: General
Flags: needinfo?(glob)
tracking-e10s: --- → +
This never got done.

Is this something we still need? If so, can the graphs be built using Telemetry data? If not, what's missing?
Flags: needinfo?(lhenry)
(Reporter)

Comment 12

4 months ago
I don't think so!
Flags: needinfo?(lhenry)
Sorry about that!

Closing as WONTFIX.
Status: NEW → RESOLVED
Last Resolved: 4 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.