Closed Bug 893926 Opened 11 years ago Closed 11 years ago

Add a memory reporter for BrowserElementParent

Categories

(Firefox OS Graveyard :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: justin.lebar+bug, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [MemShrink:P2])

We leak BrowserElementParent objects, and we think this is causing us to waste significant amounts of memory on B2G.

It would be helpful to have a memory reporter for this.

What I think we should try for is something like

2 - BrowserElementParents
  1 - BrowserElementParent(http://...)
  1 - BrowserElementParent(http://...)

where the URI is the last URI that the BrowserElementParent loaded.
Whiteboard: [MemShrink] → [MemShrink:P2]
With the latest B2G code on a DMD build I haven't seen BrowseElementParent referenced in the unreported stack trace section of the dmd logs retrieved with get_about_memory.py. On a previous build I did see it in an entry in an unreported stack trace, but it was of such a small size it seems like it's not worth effort tracking.

I tested by opening/closing several apps, running get_about_memory.py after each time.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.