> I'm seeing a major memory leak with table destruction, in 0.7.2 For those of you not following the discussion in the bug report at http://bugzilla.qooxdoo.org/show_bug.cgi?id=753 here is a summary:
There were subsidiary objects that weren't being disposed of correctly when the table was disposed. 0.7.3 will fix this problem or see the issue for a patch. If you override objects in the table, e.g. creating your own renderer and calling setDataRowRenderer(), you have to get the original object and dispose of it yourself. The recommended way of working with qooxdoo objects is to use object factories which re-use instances. See http://qooxdoo.org/documentation/general/enterprise_application for more information and other guidelines on how to structure your application. 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
