IE is famous for leaking. Also, their GC is totally decrepit, since circular references are not detected:
http://tinyurl.com/dkyec An easy way to create a leak is through a closure. I bet we have closures handling events on the image loader that are causing the leaks. Maybe try nulling all the event handlers when a load completes? On 2006-06-15, at 22:54 EDT, Henry Minsky wrote: > I ran the LZPIX app in IE6 with the task manager open showing the > amount > of RAM allocated to the > iexplorer.exe process. Every time I click on a thumbnail to display > it, > it eats about 2 MB of RAM, which > never is released. In Firefox, it consumes a much smaller amount, > maybe > 1-200k which gets GC'd the next thumbnail I click on. > > I am going to try to figure out if this is the XML data load eating > all > that memory, or what... > > > > > > _______________________________________________ > Laszlo-dev mailing list > [email protected] > http://www.openlaszlo.org/mailman/listinfo/laszlo-dev _______________________________________________ Laszlo-dev mailing list [email protected] http://www.openlaszlo.org/mailman/listinfo/laszlo-dev
