ScriptProcessorNode leak causes crash in Chrome

[ChadMcKinney]

When using Chrome ScriptProcessorNode leaks memory, eventually resulting in a crash. At the moment this looks to be a bug in Chrome and has been filed here:

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

This bug comes up when using Lich for extended periods of time. Collaborating with multiple people with expedite it. Unfortunately using a pooling technique to prevent heap overflow causes very noticeable audio glitching and is not a suitable work around.

This effects a majority of the Lich UGens such as crush, decimate, distortion, white, violet, etc... For the moment we just have to see what Google does with the bug report.