Since our problem seems related to repeatedly setting listeners on objects, even if from different other objects, I'd suggest a mixin containing a safeAddListener() method to the listener object, which, besides calling addListener() on the object generating the event, should store listeners added to foreign objects in an array, and remove them in destroy(). It could also set all members to null in destroy(), to additionally help the garbage collector. This way, no dangling listeners would stay around for an object you destroy explicitly. Some execution overhead would occur, but mem losses would be a lot less probable.
But I need to do some experiments to confirm the problem - I hope to be able to do this this year. flj ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
