Last Comment Bug 730177 - Page doing a bunch of XHR and image loading seems to never trigger GC/CC
: Page doing a bunch of XHR and image loading seems to never trigger GC/CC
Status: NEW
[MemShrink:P2]
:
Product: Core
Classification: Components
Component: JavaScript Engine (show other bugs)
: Trunk
: x86 Mac OS X
: -- normal with 1 vote (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
:
Mentors:
Depends on: 730447
Blocks:
  Show dependency treegraph
 
Reported: 2012-02-23 18:28 PST by Boris Zbarsky [:bz] (Out June 25-July 6)
Modified: 2014-07-24 11:07 PDT (History)
9 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments

Description Boris Zbarsky [:bz] (Out June 25-July 6) 2012-02-23 18:28:36 PST
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...
Comment 1 Boris Zbarsky [:bz] (Out June 25-July 6) 2012-02-23 18:30:03 PST
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
Comment 2 Andrew McCreight (PTO-ish through 6-29) [:mccr8] 2012-02-23 18:37:35 PST
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 Andrew McCreight (PTO-ish through 6-29) [:mccr8] 2012-02-23 18:43:03 PST
Kyle might also have some idea.
Comment 4 Kyle Huey [:khuey] (khuey@mozilla.com) 2012-02-23 18:44:59 PST
Sounds an awful lot like Bug 681479 to me.
Comment 5 Justin Lebar (not reading bugmail) 2012-02-24 02:09:40 PST
> 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 Olli Pettay [:smaug] (high review load, please consider other reviewers) 2012-02-24 05:57:44 PST
(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.
Comment 7 Boris Zbarsky [:bz] (Out June 25-July 6) 2012-02-24 14:46:25 PST
> 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 Justin Lebar (not reading bugmail) 2012-02-24 15:59:00 PST
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.

Note You need to log in before you can comment on or make changes to this bug.