Closed Bug 792155 Opened 12 years ago Closed 12 years ago

[ARMv6] Get and analyze about:memory dumps

Categories

(Firefox for Android Graveyard :: General, defect)

All
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: kats, Unassigned)

References

Details

(Whiteboard: [ARMv6])

If possible we should try to grab about:memory dumps from OOM crashes and analyze them to see what (if anything) is taking up too much memory, and further optimize/patch that area.
Dumping about:memory on OOM is very hard; we need memory to dump about:memory, and anyway, we could get an OOM signal at literally any point in time, and it's not necessarily safe to start an about:memory dump at any point in time. If you could get some early warning, then you could use the work in bug 788021 to dump about:memory to disk.
Whiteboard: [ARMv6]
If we can get about:memory dumps in low-memory situations it would still be useful but as it stands we probably won't get around to doing this, so I'll mark this bug closed.
Status: NEW → RESOLVED
Closed: 12 years 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.