<br><br><p><DEFANGED_div class="gmail_quote">On Nov 21, 2007 8:45 AM, Tim Schmidt <<a href="mailto:timschmidt@gmail.com">timschmidt@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" DEFANGED_style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<p><DEFANGED_div class="Ih2E3d">On Nov 21, 2007 8:39 AM, Scott Huffman <<a href="mailto:sjhuffman@gmail.com">sjhuffman@gmail.com</a>> wrote:<br>> Firefox's doesn't just have the memory problem. It also consumes<br>> abnormally large amounts of CPU usage. It's good that they are fixing
<br>> the memory leaks though.<br><br></p><DEFANGED_div>In my experience, Firefox tends to consume lots of ram, but doesn't<br>seem too leaky (I've managed to keep a single instance running for > 3<br>months at least - with hundreds of tabs open). The second you install
<br>flash or java plugins, however, it turns into a leaky steaming pile of<br>CPU cycle stealing crap. :-/<br><br>Just my 2 cents.<br><font color="#888888"><br>--tim<br></font><p><DEFANGED_div><p><DEFANGED_div></p><DEFANGED_div><p><DEFANGED_div class="Wj3C7c"> </p><DEFANGED_div></p><DEFANGED_div>
</blockquote><p><DEFANGED_div>Seems basically right. I see problems<br>when I have more than 3 to 4 windows<br>open, and when I have other than <br>certain web sites on them. It's hard to <br>sort out just exactly which is the real
<br>culprit. But as you suggest, I'd be<br>willing to believe it's more the things<br>people install after Firefox is installed<br>than Firefox itself. <br><br>It's hard to understand how the Firefox<br>people would have "300 leaks" to fix,
<br>but the project is probably a big team <br>now. Whether that solves the problem<br>for all the plugins and things brought<br>on board with different web sites is of <br>course the test. <br><br>It seems to me that things got worse
<br>between version 1 and version 2. If <br>true, perhaps it's a result of success,<br>and too many players. We'll see.<br><br> -Bob<br><br></p><DEFANGED_div></p><DEFANGED_div><br>