|
From: SourceForge.net <no...@so...> - 2003-08-13 13:53:33
|
Bugs item #787137, was opened at 2003-08-12 03:36 Message generated for change (Comment added) made by xwisdom You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105757&aid=787137&group_id=5757 Category: DynAPI 3 API Group: None Status: Open Resolution: None Priority: 5 Submitted By: Andrew Gillett (agillett) Assigned to: Nobody/Anonymous (nobody) Summary: Memory leak in DynElement.deleteChild() Initial Comment: The DynElement.deleteChild() function is implemented thus: p.deleteChild = function(c) { c.removeFromParent(); c._delete(); }; Although the _delete() function is documented in quickref.dynelement.html, it is not implemented _anywhere_ in the DynAPI source code, except for being set to dynapi.functions.Null in event.js. If you have a page that repeatedly adds and removes DynElements, it will leak memory. If you replace the call to _delete() with a call to _destroy(), the memory leak goes away: p.deleteChild = function(c) { c.removeFromParent(); c._destroy(); }; ---------------------------------------------------------------------- >Comment By: Raymond Irving (xwisdom) Date: 2003-08-13 13:53 Message: Logged In: YES user_id=696242 Are you using the lastest snapshot? What browsers are experiencing this memory leak? You can get the lastest snapshot here: http://dynapi.sourceforge.net/snapshot/?N=D ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105757&aid=787137&group_id=5757 |