> To complete the cycle (after a close) you can also dispose a window, if > you are really sure, that you don't need it anymore. The problem in this > case is, that JS itself has no possibilities to do a real garbage > collection. The only thing the qooxdoo disposer do, is to decouple > objects and html nodes from each other to allow the (buggy) garbage > collector to do its work (generally after leaving the page). So if you > open many QxWindows and dispose them (like for simple confirm dialogs) > it would be probably the best the reuse them. Otherwise the memory used > by the browser will grow and grow until you leave the page or there is > another event which starts the garbage collector.
I'm sorry but I have been using jsp for page layout and dont have a lot of knowledge of how the modern browsers handle memory allocation. It sounds like what you are saying is you can not create a large application using only one page because the system would never release the memory. Is that correct? Is the garbage collection a function of the browser? Do we have any idea when it runs? -Bob ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
