The application I'm developing has reached a point where when the browser is refreshed or closed, the qx.core.ObjectRegistry.shutdown method has to process a large number of object.dispose calls (>10000) and this causes IE to throw a script busy error.
I'm currently trying to reduce the number of objects by using singletons for common popups and ensuring that objects are disposed of as early as possible. I've also been investigating if there is a way to process the object.dispose calls using a timeout, however, using this approach, IE completes the refresh and doesn't process the callback function for the timeout which leads to undisposed objects and memory leaked. Has anyone else run into this issue? Any ideas on an approach to avoid this error occurring? Other than reducing the total number of objects, or changing the registry setting so that IE allows more statements to be executed before throwing the error. Thanks, Chris -- View this message in context: http://n2.nabble.com/Script-busy-error-in-IE-on-page-refresh-tp4588360p4588360.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
