<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><span>Safari browser on the Mac does not have this problem either the 64 bit nor the 32 bit computers.<br></span></div><div><br></div> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div dir="ltr"> <font face="Arial" size="2"> <hr size="1"> <b><span style="font-weight:bold;">From:</span></b> Robert Johnston <anaerin@gmail.com><br> <b><span style="font-weight: bold;">To:</span></b> nightly-testers@mozilla.org <br> <b><span style="font-weight: bold;">Sent:</span></b> Saturday, June 2, 2012 1:03 AM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: Abnormally high RAM usage in latest Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:15.0) Gecko/15.0 Firefox/15.0a1 build<br> </font> </div>
<br>
On 6/1/2012 4:46 PM, Alex Jordan wrote:<br>> On Fri, Jun 1, 2012 at 2:57 PM, Robert Johnston <<a ymailto="mailto:anaerin@gmail.com" href="mailto:anaerin@gmail.com">anaerin@gmail.com</a>> wrote:<br>>> It still happens with a clean profile, so it seems this isn't extension<br>>> related.<br>> See if you can reproduce with another browser, like Chrome or Safari.<br>> It sounds to me like the Google +1 button just has a big memory<br>> footprint, and if that was the case, the issue would show up in<br>> another browser too.<br><br>Chrome is reasonably stable, and doesn't leak resources no matter how long/how much GReader is used, which seems to indicate it's disposing of the "stale" references correctly.<br><br>It's not that the +1 button has a big memory footprint (it's footprint is 1.58MB per instance, which is pretty small), it's that old versions that are no longer in use (page refreshed to clear the list/scrolled off the
top of the page/internal (on-page) "refresh" process) are still being kept open. So as you scroll through your Google Reader collection (each entry of which has a +1 button) a button's IFRAME(?) is loaded, but not disposed of, making those "tiny" partitions stack up. A problem with GC, perhaps, or the items are being kept open to maintain a cache of the response (even though the items are unique and should have been destroyed some time ago)?<br><br>I will also note that, while I have only observed this behaviour with the +1 button, it's quite possible it's happening with other social media/IFRAMEd "like"/"favourite"/"share" buttons as well. This could be a major cause of the perceived "Memory Hog" nature of Firefox, and it's increasing sluggishness over time (GCing takes progressively longer and longer the more of these dangling "tiny" partitions are around - with 1,500 of them it takes around 3 seconds to GC, and that's with a 6-core CPU and 16GB of
RAM to help things along).<br>_______________________________________________<br>Nightly-testers mailing list<br><a ymailto="mailto:Nightly-testers@mozilla.org" href="mailto:Nightly-testers@mozilla.org">Nightly-testers@mozilla.org</a><br><a href="https://mail.mozilla.org/listinfo/nightly-testers" target="_blank">https://mail.mozilla.org/listinfo/nightly-testers</a><br><br><br> </div> </div> </div></body></html>