search

ffmpegwasm / ffmpeg.wasm

FFmpeg for browser, powered by WebAssembly
https://ffmpegwasm.netlify.app
MIT License
13.47k stars 776 forks source link

Mem Leak #666

Open baoziv587 opened 6 months ago

baoziv587 commented 6 months ago

When I called ffmpeg.terminate(). Then I need to use ffmpeg again, so have to call ffmpeg.load , mem goes up after you call ffmpeg.load again and again, and initialize the WASM again and again. So I guess some mem did not release when the user called terminate

"@ffmpeg/ffmpeg": "^0.12.10", "@ffmpeg/util": "^0.12.1",

Windows 11, latest Chrome and Edge

sasiik commented 2 months ago

Same issue for me. Did you find any way to optimize memory usage?

MertHaddad commented 1 month ago

up