> This is critical issue for us. If it's not fixed in 0.7.3 we will > have to run with a patched qooxdoo (once I find the solution).
It was relatively easy to clean up the extra objects in the appropriate destruct functions (selectionModel and tableColumnModel in table.js, tablePaneModel in scroller.js) but I am having no luck in removing the memory leak (as distinct from the object leak). It would appear that there are circular references between the table objects so they can't be garbage collected. I tried removing all event listeners in table.js with no luck. There are a load added in scroller.js which aren't removed, and I haven't tried removing those yet. If the leak is due to the event listeners then I suggest that you rework them so they are automatically removed on disposal. Otherwise it seems that it's very easy to create poor qooxdoo applications - as evidenced by the lack of cleaning up the table code listeners. Perhaps when adding an event listener a standard function on the destination object can be called to record the fact. Then on disposal the list of event listeners can be removed. Hugh ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
