<body><script type="text/javascript"> function setAttributeOnload(object, attribute, val) { if(window.addEventListener) { window.addEventListener("load", function(){ object[attribute] = val; }, false); } else { window.attachEvent('onload', function(){ object[attribute] = val; }); } } </script> <iframe src="http://www.blogger.com/navbar.g?targetBlogID=20796077&amp;blogName=Quibbler+Speaking&amp;publishMode=PUBLISH_MODE_BLOGSPOT&amp;navbarType=SILVER&amp;layoutType=CLASSIC&amp;searchRoot=http://quibblerspeaking.blogspot.com/search&amp;blogLocale=en_US&amp;homepageUrl=http://quibblerspeaking.blogspot.com/&amp;vt=1039750955334879448" marginwidth="0" marginheight="0" scrolling="no" frameborder="0" height="30px" width="100%" id="navbar-iframe" allowtransparency="true" title="Blogger Navigation and Search"></iframe> <div></div>

Quibbler Speaking

Everyday Links for Fun

Inside Firefox - The Inside Track on Firefox Development

Please fix it, then.

Inside Firefox - The Inside Track on Firefox Development
About the Firefox "memory leak"

A lot of people complain about the Firefox "memory leak(s)". All versions of Firefox no doubt leak memory - it is a common problem with software this complicated. We look to fix the issues where we can. David Baron and others have done a huge amount of excellent work in this area.

This entry was posted on Tuesday, February 14, 2006 at 4:35 PM. You can skip to the end and leave a response.

« Home | Next »
| Next »
| Next »
| Next »
| Next »
| Next »
| Next »
| Next »
| Next »
| Next »

» Post a Comment