Thanks for the report. Do you inow of any documentation about the memory leak? I discovered it today in my testing on both Safari and Chrome. And yet, there are a number of articles recommending recursive use of setTimeout, and at least two in stackOverflow that claim that setTimeout is the way to avoid blowing the stack during recursion.