Despite calling .destroy on the RnnoiseWorkletNode instance, I am facing a memory leak which eventually leads to the error below.
The memory leak error surfaces after creating and closing a large number of OfflineAudioContext instances, each with their own RnnoiseWorkletNode. I am making sure to destroy the RnnoiseWorkletNode of each instance with destroy()
The issue might be upstream in shiguredo/rnnoise-wasm, upgrading to the latest version might solve the issue.
workletProcessor.js:838 failed to asynchronously prepare wasm: RangeError: WebAssembly.instantiate(): Out of memory: Cannot allocate Wasm memory for new instance
(anonymous) @ workletProcessor.js:838
Promise.then
O @ workletProcessor.js:837
M @ workletProcessor.js:864
Le @ workletProcessor.js:875
(anonymous) @ workletProcessor.js:967
loadBinary @ workletProcessor.js:2306
(anonymous) @ workletProcessor.js:2451
fe @ workletProcessor.js:2457Understand this warning
workletProcessor.js:693 Aborted(RangeError: WebAssembly.instantiate(): Out of memory: Cannot allocate Wasm memory for new instance)
t @ workletProcessor.js:693
(anonymous) @ workletProcessor.js:845
Promise.then
O @ workletProcessor.js:837
M @ workletProcessor.js:864
Le @ workletProcessor.js:875
(anonymous) @ workletProcessor.js:967
loadBinary @ workletProcessor.js:2306
(anonymous) @ workletProcessor.js:2451
fe @ workletProcessor.js:2457Understand this warning
workletProcessor.js:694 Uncaught (in promise) RuntimeError: Aborted(RangeError: WebAssembly.instantiate(): Out of memory: Cannot allocate Wasm memory for new instance)
at t (workletProcessor.js:694:17)
at workletProcessor.js:845:17
Despite calling
.destroyon theRnnoiseWorkletNodeinstance, I am facing a memory leak which eventually leads to the error below.The memory leak error surfaces after creating and closing a large number of
OfflineAudioContextinstances, each with their ownRnnoiseWorkletNode. I am making sure to destroy theRnnoiseWorkletNodeof each instance withdestroy()The issue might be upstream in
shiguredo/rnnoise-wasm, upgrading to the latest version might solve the issue.