> In a common case, the handler uses a table object (with our own > remote > data model and custom row and cell renderers). When changing viewed > objects we're seeing a considerable memory leak, of the order of > 1.3MB in > IE7. > > I modified qx.dev.ObjectSummary.getInfo to show a delta - i.e. only > those > object types which increased in count were shown in the report. This > revealed that there were three objects not being disposed when the > table > object was disposed: > > 024625 DEBUG: abling.fragment.CViewer[608]: Summary: (1922 Objects) > 1: qx.ui.table.pane.Model > 1: qx.ui.table.columnmodel.Basic > 1: qx.ui.table.selection.Model
I've been able to reproduce this in the quickstart application for 0.7.2. Just slot the attached file into Application.js in the quickstart folder and open the index.html file. When you click on the button the table is removed, extra objects are shown in an alert box, and the table is created again. Second time around you see exactly the same list of items as above, and memory increases. This is obviously a critical problem and should be fixed for 0.7.3. I'll raise a bug report and spend some more time trying to track down the best way to clean up objects and memory. Hugh
Application.js
Description: Binary data
------------------------------------------------------------------------- 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
