Tuesday, September 18th, 2007p>We were all hoping that IE’s memory leaks were fixed, but Joel Webber of the GWT team dug deeper . At first he was excited of course:
When I saw this article, I nearly spilled tea all over the keyboard. They really fixed this issue? You mean I can untangle all the painful code in GWT that works around this issue, diligently cleaning up all its circular DOM references under all sorts of circumstances?
And then he had a gut check:
Before I got too excited, I had to do a little gut-check. Did they really go back and make it possible for their garbage collector to chase references through COM objects? That would be wonderful, but I’m not holding my breath.
And finally he tested it with a script to prove that IE still throws out memory all over the shop. Some things are too good to be true.
Come on IE team. For awhile you were out in the open talking to the community, and then you went back into the black hole!