Jun 13, 2011

Prototype 1.7 memory leak

Lately, I've been trying to fix a memory leak in TeamCity. After a long investigation, I found out that DOM elements on the page remains in memory even after a simple construct like:
  element.on("click", Prototype.emptyFunction).stop();

This code adds a fake event listener on a element and immediately removes it (all using Prototype javascript library).

I.e., after executing the code and removing the element from the page, it remained in browser memory.
(BTW, I used Google Chrome memory profiler to find out hanging elements).

So, the leak was caused by the Prototype's code, and I found out this nasty line:

Ironically, Prototype tries to avoid memory leak in IE by removing all event handlers on page unload, and for that, keeps a collection of the elements in the CACHE array. But, it never removes elements from the array (only on page unload), even when all event handlers are removed from an element. For any heavy ajax application, when elements are added/removed/replaced on the fly, this may be very unpleasant.

I've fixed the problem in my Prototype fork on GitHub, and added a pull request to Prototype. Hope, it will save someone some hairs.

You can also download patched prototype.js with the fix.

Update: my original fix introduced a performance problem in stopObserving method (when many elements were observed on the page). Now, the problem is fixed, all related resources above were updated.


Ran said...


is there a simple way to apply a patch ? without understanding git, etc ?
also, can't we release another prototype version with this fix ?

Ran Berenfeld


Kir Maximov said...


I've created a patched version of prototype.js and included the link at the bottom of the blog post.

Thanks for the hint :)


yul1a said...

Thank you, but I still receive Stack OverFlow in IE..