Hi Jason, Am 19.02.2007 um 16:27 schrieb Priebe, Jason:
> Is there a convenient way to dispose all the objects in this global > object db when the user navigates away from the qooxdoo application's > page? This is already the case. Every object in the DB is disposed on page unload (which is one of the reasons why the DB exists in the first place). Usually, the object DB is a good thing because you (the developer) don't have to make sure that everything is disposed in the end. However, if you're creating lots of qooxdoo objects _without_ reloading the page inbetween (as seems to be the case for the guy who opened this thread), you have to make sure that you call dispose() on them when you no longer need them. The reason why the dispose() method exists at all is because of memory leaks in browsers. By setting all sorts of references to null inside dispose(), the garbage collector can (hopefully) better free the memory occupied by objects. To summarize: The object DB helps to solve memory leak problems in current browsers. However, it also creates additional references to the managed objects so they won't be garbage-collected before page unload or dispose() is called on them (which removes the reference from the DB). You can also create objects which don't get recorded in the DB at all (see the qx.core.Object constructor), but you can only do that for your own classes, not the ones in the framework. Regards, Andreas ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
