`resize` event listeners for subfolders outlive destruction of the gui

I noticed an apparent memory leak in an application that was repeatedly updating a dat.GUI in a loop, and I believe it may be due to the ever-increasing number of resize event handlers added to the window. Obviously creating and destroying guis in a tight loop is not a great idea, but I’d still like to at least make sure the program doesn’t leak memory.

To reproduce, using the latest dat.gui.js, simply run in the console:

for (let i = 0; i < 1000; i++) {
    gui = new dat.GUI();
    let f = gui.addFolder("hello");
    gui.destroy();
}

then inspect getEventListeners(window).resize and observe that 1000 new elements have been added. Calling gui.removeFolder(f) appears to make no difference. It seems like f.destroy() should fix the problem, since it unbinds the resize listener, but that actually fails:

for (let i = 0; i < 1000; i++) {
    gui = new dat.GUI();
    let f = gui.addFolder("hello");
    f.destroy();
    gui.destroy();
}

dat.gui.min.js:13 Uncaught DOMException: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.
    at e.destroy (http://127.0.0.1:5010/js/dat.gui.min.js:13:45356)
    at <anonymous>:4:4

Can you give me any advice? Thanks!

[technbuzz]

My mistake, somehow the prototype of gui.removeFolder was modified accidently. All the events are properly removed now with gui.destroy()

[technbuzz]

I am using the very latest version.