Am 01.08.2006 um 20:08 schrieb Erik A. Onnen: > Admittedly I'm ignorant as to the internals of the IE garbage > collector, but shouldn't simply nulling out the qx.core.Object._db be > sufficient for escape analysis (i.e. if this is the only point of > reachability for these objects, removing it should preclude any it's > contents from being marked as reachable)?
Sorry, I didn't read your statement carefully enough before my first reply. The problem is that somewhere inside the object DB, there may be a JavaScript object that has a reference to a DOM object (which again might have references to JavaScript objects). This cycle isn't broken by just getting rid of the main DB reference. So the answer to your question is: Nulling out is sufficient (i.e. you don't need to use the "delete" operator), but you have to null out everything recursively! Oh, and I think I missed a crucial point why your IE delete time is so high. It's probably not because of the garbage collector, but because the array gets reorganized on every delete (since an index is actually removed from it as opposed to simply assigning a new value). Looks like Firefox is way more efficient here ... 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 [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
