[dojo-contributors] IE7 leaks and testBench

Michael Schall mike.schall at gmail.com
Wed Aug 8 20:04:38 EDT 2007

In my widgets I break those links in the widget's uninitialize

uninitialize: function() {
    try {
        this.containerNode = null;
    } catch (e) {}
    //call to super

Most of these pointers are from the dojoAttachPoints is there an array
or something of attachPoints on a widget that could be looped
generically to null them out?

On 8/8/07, Bill Keese <bill at dojotoolkit.org> wrote:
> Michael Schall wrote:
> > A leak is shown using sIEve.  I attached this to the IE7 speed ticket...
> >
> > http://trac.dojotoolkit.org/ticket/4046
> >
> I've been tracing the sIEve output.   Apparently the problem is that
> Widget.destroy() orphans the widget's dom node, but there are still
> pointers from the widget object to those nodes (like containerNode).
> Just commenting out the call to destroyRendering() seems to stop the
> leak but I'm not sure if that's a good long term solution.
> The problem gets more complicated with widgets that contain other widgets.
> _______________________________________________
> dojo-contributors mailing list
> dojo-contributors at dojotoolkit.org
> http://dojotoolkit.org/mailman/listinfo/dojo-contributors

More information about the dojo-contributors mailing list