Closed Bug 661571 Opened 13 years ago Closed 5 years ago

Handle histogram conflicts gracefully

Categories

(Toolkit :: Telemetry, defect)

Product:
Toolkit
Component:
Telemetry
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: taras.mozilla, Unassigned)

References

Details

The chromium histogram code sanity checking causes aborts in debug mode (or returns NULL in release mode). This happens when 
a) requesting a histogram with the same name but with different parameters to how that histogram was initially declared.
b) requesting invalid parameters

Currently nsITelemetry has extra checks to return codes in case of b). a) still needs to be addressed
I'm interested in this bug. Can someone tell how to proceed with this bug? Thanks!!
Component: General → Telemetry

We've built out Telemetry a "little" bit in the past 8 years so this is no longer a valid concern. Telemetry Histograms are forbidden by policy from changing while maintaining the same id for fear of pipeline impact, and access to chromium histogram code is wrapped by Telemetry.

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