Closed Bug 1571833 Opened 5 years ago Closed 5 years ago

Mission Control Dashboard not detecting large spike in macOS crashes on 68 release

Categories

(Cloud Services :: Mission Control, defect)

68 Branch
Unspecified
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: marcia, Unassigned)

Details

Noticed today when inspecting crash stats and mapping to Mission Control.

Top crash https://bugzilla.mozilla.org/show_bug.cgi?id=1570451, with over 10K in combined signatures doesn't show up on the MC release dashboard - https://missioncontrol.telemetry.mozilla.org/#/?channel=release.

It is detected on both nightly (https://missioncontrol.telemetry.mozilla.org/#/nightly/mac) and beta (https://missioncontrol.telemetry.mozilla.org/#/beta/mac).

On the Socorro side, it is the top overall crash on both nightly and beta. On release it is the #2 overall crash after the OOM signature.

Do we know why it is not detected on release?

Adding Will in case he can help us understand why.

Flags: needinfo?(wlachance)

(In reply to Marcia Knous [:marcia - needinfo? me] from comment #1)

Adding Will in case he can help us understand why.

You can definitely see it go up in the detail view over the past few days, but it's probably not severe enough to be noticeable amidst the very large amount of accumulated data we already have for release 68.

https://missioncontrol.telemetry.mozilla.org/#/release/mac/main_crashes?aggregateLength=24&timeInterval=1555140&relative=0&percentile=99&normalized=0&disabledVersions=&versionGrouping=version

Showing the rate over a shorter time interval (e.g. the last 48 hours) would make this sort of thing more obvious, we've discussed doing this before (e.g. https://github.com/mozilla/missioncontrol/issues/318). Also something for :saptarshi and :wbeard to take into account when building their model for Mission Control v2.

Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(wlachance)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.