Open Bug 1316793 Opened 8 years ago Updated 2 years ago

Handle out-of-space states better when capturing stacks

Categories

(Toolkit :: Telemetry, defect, P3)

Product:
Toolkit
Component:
Telemetry
Type:
defect

Tracking

()

People

(Reporter: yarik.sheptykin, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [measurement:client])

Currently, when we the number of captured stacks exceeds `kMaxChromeStacksKept` we start do drop any further captures. We can do better than that.
Depends on: 1225851
Summary: Handle out of space states in capturing stacks in telemetry → Handle out-of-space states better when capturing stacks
(In reply to Iaroslav Sheptykin from comment #0) > Currently, when we the number of captured stacks exceeds > `kMaxChromeStacksKept` we start do drop any further captures. We can do > better than that. Can you expand on what improvements you are thinking of?
Priority: -- → P3
Whiteboard: [measurement:client]
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.