Hi Stefan, thank you for sharing these results. We will have a very close look at the memory consumption of your script. I would not be surprised if the base line memory consumption of the qooxdoo app is above GWT and dojo as qooxdoo widgets are probably more complex than those. But the increase of memory consumption looks like a serious dispose bug somewhere in our widget code, which we have to fix. We'll keep you up to date.
BTW to my knowledge the RAP guys at Innoopract are working to add widget pooling in the next 0.8 based RAP release. Best Fabian > Hi there, > we are working on a bigger RAP application and as others do face the > problem, that memory consumption of a single-page application > increases very fast in IE. > > To track bugs down I started to write a really simple qooxdoo-test-app > trying to reproduce the problem and this wasn't to hard to achieve > just by creating and destroying a lot of qx.ui.basic.Labels's in a row > (and doing nothing else which could cause a leak). > > After 3000 Labels the IE7 memory is over 180MB (testet with 0.7.3 and > 8.0). Considering the Label to be one of the simplest qooxdoo-widgets, > I think this is unacceptable. > > The last 3 days I read a lot about IE memory problems, lazy garbage > collection, circular references, object pooling and the like ... > nevertheless I came to the conclusion that though it might not be > easy, even without object pooling it should be possible to have a > constant memory consuption in IE7 in the above scenario. > > As sort of a proof I built the scenario (creating/destroying a simple > widget a lot of times) with dojo-toolkit'-Textbox and Google Web > Toolkit-Labels. > Both don't have any sort of object pooling and both leave IE7s memory > constantly under 27MB (GWT) or 55MB (dojo) even for >20.000 (!) > created and destroyed widgets (though Dojo seems to leak a VERY tiny > bit as well). This is a huge difference to qooxdoo for sure. > > I'm not sure, whether I'm doing anything wrong with qooxdoo. I played > around with calling 'destroy' und 'dispose'-functions, flushed the > qx.core.queue.Dipose-object and did several other things - nothing of > which helped. > > Can anyone give me hints of what to do in qooxdoo to have a constant > memory allocation ? > I now that object pooling might be a way, BUT in my opinion object > pooling in this case is just hiding the fact that there is a memory > problem. > > I planned to provide my qooxdoo-(0.8)-script, as well as GWT and Dojo > examples of the same scenario as a comparison. > Unfortunataly the newsgroup doesn't accept this - any idea how i can > provide this ? > > > Your help is much appreciated. > > Kind Regards, > Stefan Hansel > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > ------------------------------------------------------------------------ > > _______________________________________________ > qooxdoo-devel mailing list > qooxdoo-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > -- Fabian Jakobs JavaScript Framework Developer 1&1 Internet AG Brauerstraße 48 76135 Karlsruhe Amtsgericht Montabaur HRB 6484 Vorstand: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich, Thomas Gottschlich, Matthias Greve, Robert Hoffmann, Markus Huhn, Oliver Mauss, Achim Weiss Aufsichtsratsvorsitzender: Michael Scheeren ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
