The bottom line seems to be that closures are very expensive in IE. Therefore, QooxDoo shouldn't be creating them by default for every object created when debug is on, as I said earlier.
Objects that there will be many of also should not use addListener or qx.lang.Function.bind, as these create closures too. This blog post: http://laurens.vd.oever.nl/weblog/items2005/closures/ talks about a clever way to re-use closures so you don't get memory leakage in IE. Might be applicable in qx.Class, though I'd have to think about it more to be sure. Dave -- View this message in context: http://qooxdoo.678.n2.nabble.com/Instantiated-object-memory-usage-under-IE-tp5979072p5983047.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
