Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Ffmpeg.wasm not working in Chrome extension due to SharedArrayBuffer
See original GitHub issueDescribe the bug I can’t seem to be able to use ffmpeg.wasm in a chrome extension anymore.
To Reproduce
I simply used the example from https://github.com/ffmpegwasm/chrome-extension-app and loaded it into
my chrome as an extension, this now throws an Uncaught (in promise) ReferenceError: SharedArrayBuffer is not defined error.
I’ve also attempted to run ffmpeg.wasm from the sanbox environment of a chrome extension, but it resulted in the
same error.
Expected behavior A working example of ffmpeg.wasm running inside of a chrome extension (preferably locally hosted).
Desktop (please complete the following information):
- OS: Windows 10
- Browser: Chrome & Brave
- Version: Chrome 92.0.4515.107 & Brave 1.27.109
Issue Analytics
- State:
- Created 2 years ago
- Reactions:6
- Comments:5
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hello, I want to ask about the progress for single-thread
I went through the process of implementing FFmpeg.wasm in an extension… There are a few caveats, but it is possible.
An example extension with a possible implementation on Manifest V2 (both on Chrome and Firefox): https://github.com/brunoluiz/gifsane-extension Post explaining some of the implementation details: https://brunoluiz.net/blog/2022/jan/gif-sane-playback-control-ffmpegwasm/