title: addEventListener memory leak due to frames
body: <p>I have a GreaseMonkey script that works on a site that uses frames as an integral part of its interface.  This script leaks memory like a sieve, and I believe it is due to my use of addEventListener within one of the frames.  Quite simply, I attach a variety of event listeners, then the frame reloads and I attach the event listeners, and then the frame reloads, around and around for hundreds or possibly thousands of iterations as you interact with various elements in this frame or others.  By the end of it, Firefox has gone from ~300M of memory to as much as 2G (or crashes before it gets there).</p>
  
  <p>I read somewhere that doing a full page reload would allow FireFox's garbage collection routines to kick in and recover all the memory from orphaned event handlers, and sure enough when I hit F5 after my script has run for a while, within about 10 seconds the memory is back down to 300M.  Unfortunately this breaks a different frame in the site (a very popular chat window), so while it does seem to confirm my suspicion that addEventListener is to blame, it's not really an option as a solution.</p>
  
  <p>Is there something else I can do to free up the memory properly without forcing a full page refresh?</p>
  
  <p>(Currently using GM 1.5 and FF 17, but the issue has existed since GM 0.8/FF 4 or thereabouts.)</p>