You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
importwaafrom"web-audio-api"importaxiosfrom"axios"consturl="https://music.163.com/song/media/outer/url?id=1991012773.mp3"// audio urlconstcontext=newwaa.AudioContext()axios.get(url,{responseType: "arraybuffer"}).then((res)=>res.data).then((buffer)=>{context.decodeAudioData(buffer,(audioBuffer)=>{// do something ... },(err)=>{// do something ...},)});setTimeout(()=>{},10000)
Then in the TaskManager, this Node.js process will occupy over 250 MB of memory.
I guess that there is a problem with the decodeAudioData function in the lib/utils.js, or is there any problem with my sample code?
By the package heapdump, I found that the AudioBuffer generated by the AudioContext.decodeAudioData function usually occupies over 50 MB of memory when the source audio file is less than 10 MB. Is that normal?
The text was updated successfully, but these errors were encountered:
BHznJNs
changed the title
There may be a memory leak problem with the AudioContext.decodeAudioData.
Is the AudioBuffer occupies too huge bytes?
Feb 19, 2023
Development environment:
Windows 11
Node.js v18.12.0
web-audio-api package version 0.2.2
Sample code
Then in the TaskManager, this Node.js process will occupy over 250 MB of memory.
I guess that there is a problem with the
decodeAudioData
function in thelib/utils.js
, or is there any problem with my sample code?By the package
heapdump
, I found that the AudioBuffer generated by theAudioContext.decodeAudioData
function usually occupies over 50 MB of memory when the source audio file is less than 10 MB. Is that normal?The text was updated successfully, but these errors were encountered: