![]() Therefore this is almost certainly not a Web Audio API/browser bug. ![]() If you set a variable holding an audio buffer to null the memory is typically purged within seconds by the garbage collector. I know those MDN docs recommend short sound files but in practice on a decent machine Chrome handles larger audio files beautifully and I often work with tracks >1 hour in length as decoded buffers with the Web Audio API with no issues. This is most apparent when using large audio files. ![]() I can confirm that Wavesurfer is erroneously not releasing the audio buffer after a call to destroy(), which results in the buffer not being garbage collected and persisting in memory even after subsequent calls to load() different sound files using the same Wavesurfer instance. Hello, I've been noticing this same issue on my end (Win 10, latest Chrome, latest Wavesurfer). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |