Hello Sebastian, This may not be relevent to the IE memory problems in qooxdoo.
I did some research yesterday and found the following undocument global method in IE: CollectGarbage(); Apparently this forces the IE GC to run. Unfortunately this will NOT solve all the memory problems in IE. What I read (which I'd never heard before) indicates that attaching JS function closures in IE onto DOM nodes (eg, event handlers such as onload etc) will leak both objects if you have a circular reference because DOM nodes have a different GC than JS objects and they don't deal with circular references caused by closures. You need to remove the function closure before unreferencing the DOM node. In most cases Qooxdoo seems to do this although some of the examples leak under IE (eg, Image1 works fine, GalleryList1 leaks ~1.5MB per refresh) so there may be some cases where this happens. The qooxdoo app I'm working on runs fine under FF, but under IE one particular page leaks 30MB per reload and dozens of MB using the page and quickly slows to a crawl, so I'd better spend some time to modify my code and see if I can find any leaks I can attibute to specific qooxdoo objects. regards --- Simon Cope Chief Software Architect ER Mapper Phone: +61 8 9388 2900 Fax: +61 8 9388 2901 Email: [EMAIL PROTECTED] Mosaic, Balance and Compress your images with new ER Mapper MBC Visit: www.ermapper.com for details http://www.earthetc.com ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Qooxdoo-devel mailing list Qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
