http://weblogs.asp.net/bleroy/archive/2007/06/26/ie6-s-main-memory-leak-hot-fixed.aspxI just learned through Ajaxian that IE6's main memory leak has been hot-fixed two weeks ago through Windows Update . So what does that mean for Ajax developers? Well, it becomes a little less important to dispose of any circular references you may haveenCommunityServer 2007 SP1 (Build: 20510.895)http://weblogs.asp.net/bleroy/archive/2007/06/26/ie6-s-main-memory-leak-hot-fixed.aspx#6764853Thu, 04 Dec 2008 00:10:01 GMTc06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:6764853Bertrand Le RoyBertrand Le Roy<p>@Shankar: just clean after yourself. If you're using building Microsoft Ajax, that means implementing dispose on all your components. In general, avoid capturing elements in closures. The above example can be cleaned by deleting the expando on the element.</p> <img src="http://weblogs.asp.net/aggbug.aspx?PostID=6764853" width="1" height="1">http://weblogs.asp.net/bleroy/archive/2007/06/26/ie6-s-main-memory-leak-hot-fixed.aspx#6763855Wed, 03 Dec 2008 12:02:56 GMTc06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:6763855shankarshankar<p>hi, </p> <p>thx for this article . but can i get a solution for it.</p> <p>i am completely using ajax on my web site and its tending to slow my website</p> <img src="http://weblogs.asp.net/aggbug.aspx?PostID=6763855" width="1" height="1">