Closed
Bug 807363
Opened 12 years ago
Closed 12 years ago
Facebook flyout document uses too much memory
Categories
(Firefox Graveyard :: SocialAPI: Providers, defect, P1)
Firefox Graveyard
SocialAPI: Providers
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Gavin, Unassigned)
References
Details
(Whiteboard: [MemShrink:P2])
Re-posted from Asana: Looking at the memory reports in about:memory, most frames seem to be consuming a reasonable amount of memory, except the ticker flyout. Here is the breakdown: - content panels (jewels): 4 to 6mb each - sidebar: 9mb - worker: 16mb - ticker flyout: 41mb It would be great if the worker could also get leaner in the longer term, but the ticker is what's most concerning at the moment. 41mb seems a lot of memory for it
Updated•12 years ago
|
Whiteboard: [MemShrink]
Updated•12 years ago
|
Priority: -- → P1
Version: unspecified → Trunk
Updated•12 years ago
|
Whiteboard: [MemShrink] → [MemShrink:P1]
Updated•12 years ago
|
Whiteboard: [MemShrink:P1] → [MemShrink:P2]
Comment 1•12 years ago
|
||
We looked at this and we weren't deleting old DOM nodes for content you had displayed a while back and that weren't relevant anymore. We're now removing those and only keeping the 10 most recently shown divs so that should hopefully reduce memory usage a lot over time.
Comment 2•12 years ago
|
||
(This fix will go live next week).
Reporter | ||
Comment 3•12 years ago
|
||
Awesome, thanks Florian!
Reporter | ||
Updated•12 years ago
|
Keywords: push-needed
Reporter | ||
Comment 4•12 years ago
|
||
So this has definitely improved - I now see reduced usage for the flyout panel (usually not more than 20MB). But I still see higher use after displaying a few entries and waiting a bit, which makes me think that maybe recently viewed content is being cached in that document longer than it needs to?
Reporter | ||
Updated•12 years ago
|
Updated•6 years ago
|
Product: Firefox → Firefox Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•