Closed Bug 1744500 Opened 2 years ago Closed 2 years ago

[MissionControl v2] sudden drop in content crashes not aligning with crash-stats.mozilla.org data

Categories

(Data Platform and Tools :: General, defect)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: aryx, Unassigned)

References

Details

  1. Open https://metrics.mozilla.com/public/sguha/mc2/missioncontrol_v2.html
  2. Switch to the "Nightly" tab.
  3. Look at the graphs for "Content Crash Rate" and "Content Crash Incidence".

There is a drop in content crashes starting with the 20211120 builds but it's still a slope - might this be an issue which depends on the submission date of the crash reports?

https://crash-stats.mozilla.org/topcrashers/?product=Firefox&version=96.0a1&days=14&_range_type=build doesn't report such a drop (switch between 14 and 28 days to see the difference, look at the "Count" and "Installs" columns).

Does the script which generates the report throw any errors (or the import of data into the data source which it uses)?

If I'm reading the bug comments right, the underlying issue is covered in bug #1744533. I'm going to make this depend on that.

Depends on: 1744533

As mentionned above, when I saw your messages on matrix, I linked the reduction to the recent landing of my patch since it was somehow touching some crash-telemetry. Bug 1744533 fixed a few items in this matter, and it is landed on central. Hopefully things should be back to normal soon.

As much as I could investigate, Mission Control v2 should only rely on telemetry data, and I could not find any other source of mistake after landing the fix. Sorry it went under the radar.

Sebastian, from the datapoint of December 7th, data seems to be recovering back to normal ?

Flags: needinfo?(aryx.bugmail)

Thank you, it's fixed by bug 1744533.

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