Each time an Editor (or SimpleEditor) instance is created and then destroyed, memory is leaked.

Take the following snippet which repeatedly creates and then destroys a Panel instance. No memory is leaked.

var x;
setInterval(function(){
if (x) {
x.destroy();
x = null;
}
else {
var node = document.createElement('div');
document.body.appendChild(node);

x = new YAHOO.widget.Panel(node, {
height: '300px',
width: '522px'
});
x.render();
}
}, 2000);

Now try the same thing with Editor:

var x;
var node;
setInterval(function(){
if (x) {
x.destroy();
x = null;

// manually remove node because SimpleEditor's destory() method
// doesn't do it for us (unlike Panel)
YAHOO.util.Event.purgeElement(node, true);
document.body.removeChild(node);
}
else {
node = document.createElement('div');
document.body.appendChild(node);

x = new YAHOO.widget.SimpleEditor(node, {
height: '300px',
width: '522px'
});
x.render();
}
}, 2000);

I'm seeing ~1.5Mb per create/destroy cycle in FFx 3.0.5 (Ubuntu), Opera 9.62 (Ubuntu) and Chrome 1.0.154.36 (WinXP) and predictably, about an order of magnitude worse on IE7 (WinXP).

Under Ubuntu browser memory usage is easily observed via the top command. Under WinXP the task manager was used (iexplore.exe memory) and under Chrome the built-in Task Manager makes the phenomenon
even more apparent (per-tab memory usage).

A html file is attached that reproduces the bug.

Regards,

Patrick Donelan
http://patspam.com