Wasn't the bug only happening in FireFox? I mean sure, maybe it wasn't doing that on Linux, but if it's doing it on Windows and no other browsers are, then it's a memory leak.