Closed Bug 942612 Opened 8 years ago Closed 1 year ago

Prune forgotten pending crash reports


(Firefox for Android Graveyard :: General, defect, P5)




Tracking Status
fennec + ---


(Reporter: jwatt, Unassigned)



(Keywords: memory-leak, perf)

Spinning this off as a sub-bug of bug 942609. It seems that Firefox Mobile
can fail to upload pending crash reports and just leave them around forever. In my case the pending crash reports were using up almost half of the Storage that Application Manager reported Firefox as using. See:
Given mfinkle assigned bug 933979 to Wes and this is essentially a subbug of that bug, taking the liberty of assigning Wes to this one too.
Assignee: nobody → wjohnston
tracking-fennec: --- → ?
tracking-fennec: ? → +
No longer blocks: fatfennec
Wes, is this still on your plate?
Flags: needinfo?(wjohnston)
Summary: Stop Firefox Mobile from leaking Storage space by forgetting about pending clash reports → Prune forgotten pending crash reports
Being kind to Wes's queue. We'll hit this in Bug 1045887.
Assignee: wjohnston → nobody
Flags: needinfo?(wjohnston)
filter on [mass-p5]
Priority: -- → P5
Re-triaging per

Needinfo :susheel if you think this bug should be re-triaged.
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly]( an issue can be reported at the [Fenix GitHub project]( If you want to discuss your report please use [Mozilla's chat]( server and join the [#fenix]( channel.
Closed: 1 year ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.