Am 01.08.2006 um 23:09 schrieb Sebastian Werner: > Andreas Junghans schrieb: >> Am 01.08.2006 um 21:44 schrieb Erik A. Onnen: >> >>> Andreas Junghans wrote: >>>> This is the one and only reason why dispose code is >>>> necessary at all. >>> Could there not be browser-specific code in the unload to skip the >>> mass disposal in FF? It's the Stop Script/Continue dialog that's >>> killing me atm. Or maybe default as is but provide a configuration >>> hook if users wanted to bypass it for certain browsers? >> >> In the past, Firefox had some leak problems too, but I think they're >> mostly sorted out. Maybe it would really make sense to call the >> dispose code in IE only. The way it's handled now, it's a bit of a >> safety net in case other browsers have similar problems. > > Mhh, have you any reference that tell us that?
Just anecdotal "evidence". Applications we've been developing never brought Firefox 1.0.7 and up to its knees (even with incomplete cleanup code after hours of reload after reload). The same code made IE unusable pretty fast. This is why I got the impression that there are no significant leaks in current versions. > Please remember however that "dispose" isn't a memory management tool. > To just dispose doesn't free up memory. This means that long-running > application could be problematic (these applications generally creates > even more objects while running: events, io-stuff, tooltips, ...). > Just > dispose them, doesn't free up memory. So it will increase over the > runtime of the application. This is just normal I think. Not quite my point of view :-) I think an application should be able to run continuously without ever-increasing memory usage. An initial increase is normal, but there has to be a plateau somewhere, not an ever-growing mountain. As for "dispose doesn't free up memory": Of course it does (or at least it should). IMHO, when you dispose an object, all references from it (and also to it, at least as far as internal qooxdoo stuff like the object db is concerned) should be removed so that the garbage collector can reliably kill it. This way, you can create and remove widgets dynamically as much as you like. If qooxdoo really doesn't allow that, I think that is a bug and should be fixed. 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
