Closed Bug 1591965 Opened 5 years ago Closed 5 years ago

Investigate lib-crash invalid value errors in Fenix

Categories

(Data Platform and Tools :: Glean: SDK, task, P1)

Unspecified
Android
task

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: travis_, Assigned: travis_)

References

Details

(Whiteboard: [telemetry:glean-rs:m11])

Attachments

(1 file)

No description provided.
Assignee: nobody → tlong
Priority: P3 → P1
Whiteboard: [telemetry:glean-rs:m?] → [telemetry:glean-rs:m10]

The way that this is implemented in lib-crash, it's counting all of the recorded errors in the persisted file and then calling add(<number of errors>), which could potentially be zero, and calling add(0) is an invalid_value error.

Attached file GitHub Pull Request
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Blocks: 1592053

This is still happening at a low/lower frequency, reopening this to investigate again.

Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Whiteboard: [telemetry:glean-rs:m10] → [telemetry:glean-rs:m11]

Looking at this more closely using our error dashboards, it doesn't appear that we have had an instance of this occur in Fenix nightly since the 19th, and have seen a sharp falloff of occurrences just before that. This is even better if filtering for versions of Fenix using Glean-core.

Even looking at this in FF-Preview Release, we are starting to see a downward trend in both counts and affected clients.

Based on Nightly showing little or no occurrences, and based on the trend in Release towards zero, I'm closing this as fixed.

Status: REOPENED → RESOLVED
Closed: 5 years ago5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: