letz at grame.fr
Tue Sep 22 11:20:27 PDT 2015
> Doesn't matter what shape the code is. Parsing and compiling code requires memory allocation. JSC will parse and compile the code lazily, so we will continue to allocate memory after the code has already started executing.
OK, but our code already has a similar issue when deployed in a WebAudio API ScriptProcessor node (and that should probably be similar when any kind on "dynamically created" ScriptProcessor is done). We hear a few audio glitches until the code is "warm" I guess (compiled with FTL maybe?). You can test here :
It seems FireFox for instance is more robust in this area: less audio glitches at the beginning.
> We don't usually make such predictions. It would be useful to know if this API would help your use case.
Yes this API is certainly helpful.
More information about the webkit-dev