<br><br><div class="gmail_quote">On Nov 14, 2007 8:13 AM, scoob8000 <<a href="mailto:scoob8000@gmail.com">scoob8000@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Nov 12, 2007 1:24 PM, Zach <<a href="mailto:netrek@gmail.com" target="_blank">netrek@gmail.com</a>> wrote:<br></div><div class="gmail_quote"><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>> What do you consider an insane amount of physical ram?<br><br></div>I have 256MB and I've seen Firefox eat up 255MB.<font color="#888888"></font></blockquote></div><div><br>Wow! The worst I've yet seen is here on my work PC, using nearly 180MB with multiple tabs open.
<br><br>Do you have any addon's installed? I've noticed some seem to eat up the memory. Also if a browser session<br>stays open for a long time (days on end) the memory usage begins to grow.<br><br>In fact, just now I looked at my work PC. I'm at 166MB and growing, and FF has been open since last Friday.
<br>Just to test, I restarted FF. With all the same exact tabs open, I'm down to 48MB.<br></div></div></blockquote><div><br>I believe a lot of that particular memory difference is attributable to the cache of previous page states that FF keeps, to optimize the "back" feature. I seem to recall some huge complaints around the
2.0 alpha period about this, because closing the tabs doesn't necessarily release all the resources (because of the "undo close tab" feature, I think).<br><br>Like most things in software development, it's a tradeoff. Memory, speed, and features are the three knobs, but they're always non-orthogonal controls.
<br><br>Or, as it's usually stated, small, fast, or cool: pick two. :-)<br></div></div><br>-- <br>Tim Lesher <<a href="mailto:tlesher@gmail.com">tlesher@gmail.com</a>>