Closed
Bug 730177
Opened 12 years ago
Closed 14 days ago
Page doing a bunch of XHR and image loading seems to never trigger GC/CC
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
INACTIVE
People
(Reporter: bzbarsky, Unassigned)
References
Details
(Whiteboard: [MemShrink:P2])
STEPS TO REPRODUCE: 1) Load http://material.ly/products/547 2) Hold down the right arrow key for a bit. Or just hit that key every so often. ACTUAL RESULTS: As the page loads images, memory usage continues to climb, getting up over a gigabyte for me pretty easily. Opening about:memory and telling it to minimize memory usage releases all the memory. EXPECTED RESULTS: GC or CC should happen sometime...
Reporter | ||
Comment 1•12 years ago
|
||
Also, if there is any way to work around this in the page, the page author would love to know in http://stackoverflow.com/questions/9366825/firefox-specific-memory-increases-in-heavy-ajax-app
Updated•12 years ago
|
Whiteboard: [MemShrink]
Comment 2•12 years ago
|
||
Olli jiggered with how XHR stuff interacts with the CC in the last week, but I assume some random person on the internet probably isn't running Nightly. Justin, does this sound like an image-suck bug? The scenario here sounds vaguely like bug 679775. I can look into how GC/CC scheduling is working (or otherwise) on this page if it isn't just badness about the way images are being handled.
Comment 3•12 years ago
|
||
Kyle might also have some idea.
Sounds an awful lot like Bug 681479 to me.
Comment 5•12 years ago
|
||
> ACTUAL RESULTS: As the page loads images, memory usage continues to climb, getting up
> over a gigabyte for me pretty easily.
bz, were you seeing uncompressed image memory usage, or just compressed? If you ask about:memory just to GC/CC (not minimize memory usage), does it release all compressed in addition to uncompressed?
(Minimize memory usage should release all background uncompressed images unconditionally.)
I tried reproducing myself, but my internet connection here is way too slow.
Comment 6•12 years ago
|
||
(In reply to Andrew McCreight [:mccr8] from comment #2) > Olli jiggered with how XHR stuff interacts with the CC in the last week, but > I assume some random person on the internet probably isn't running Nightly. That affects only certainly alive XHRs. And yes, this sounds like Bug 681479.
Reporter | ||
Comment 7•12 years ago
|
||
> bz, were you seeing uncompressed image memory usage, or just compressed?
Mostly uncompressed.
gc/cc releases some of the uncompressed memory, but not all.
And now I can't seem to get this to go above 600MB or so... :(
Comment 8•12 years ago
|
||
If some but not all the uncompressed memory is released on gc/cc, then this sounds like a combination of bug 681479 and bug 679775.
Depends on: 730447
Whiteboard: [MemShrink] → [MemShrink:P2]
Assignee | ||
Updated•10 years ago
|
Assignee: general → nobody
Updated•2 years ago
|
Severity: normal → S3
Updated•14 days ago
|
Status: NEW → RESOLVED
Closed: 14 days ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•