ScriptProcessorNode memory leak

Hello all,
First I want to apologize if this is the incorrect venue for asking about
development issues. I am having problems with ScriptProcessorNodes leaking
memory. Here is a small example:

http://jsfiddle.net/dXjK5/

This will cause a large chunk of memory to get allocated, but in Chrome it
seems to never go away and in FireFox it seems to get collected eventually.
My question is, is there something I've done wrong here for it not to get
collected in Chrome? Is there a way to form this example so the memory does
get collected? Is this possibly a bug in Chrome or have I messed this up
some how?

I put a question on StackOverflow which you can find here (unfortunately no
one has answered):

http://stackoverflow.com/questions/23981474/scriptprocessornode-memory-leak

I also filed a bug report for Chrome in case this was really a bug:

https://code.google.com/p/chromium/issues/detail?id=379753&q=scriptprocessornode&colspec=ID%20Pri%20M%20Iteration%20ReleaseBlock%20Cr%20Status%20Owner%20Summary%20OS%20Modified%20Opened

I was hoping I'd either get a confirmation or some direction for how to
make it work correctly, but no one from the chromium team has responded
since I posted it over two weeks ago. Any guidance or help would be greatly
appreciate.

Thanks,

Chad

Received on Thursday, 19 June 2014 09:31:17 UTC