-
-
Notifications
You must be signed in to change notification settings - Fork 875
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Android WebAssembly.Memory() #133
Comments
I believe that headers should be set in your node.js server, not in browser. But I may be wrong. See - #102 (comment) |
+1 |
@ivanburlakov you need enable "cross-origin isolated" for SharedArrayBuffer feature https://web.dev/why-coop-coep/ |
isn't it what I mentioned above? Or am I missing something? |
jajaj disculpas, no leí el codigo. A mi me daba error en android igualmente y supuse que era por la memoria que se le daba a la variable INITIAL_MEMORY al hacer el build de ffmpeg, testié dando solo 250mb (aprox) y funciona en android con chrome 88.0.4324.152 en mi fork está el artifact para poder descargarlo https://github.com/EstebanFuentealba/ffmpeg.wasm-core/blob/06786fe3d4a746c03beecbc463a22415733c8632/wasm/build-scripts/build-ffmpeg.sh#L24 Saludos! |
If understood right - it works if you build |
Did you succeed, @ivanburlakov ? |
I did not work with ffmpegwasm for a while. |
Guyssss! FFMPEG started working on chrome android from version 11.4 !!! |
Describe the bug
using chrome 88 for android we get an memory issue
To Reproduce
Steps to reproduce the behavior:
Smartphone (please complete the following information):
Additional context
as of chrome 88 Shared Array Buffers are to be enabled as default (See https://www.chromestatus.com/feature/5171863141482496 https://www.chromestatus.com/feature/4570991992766464)
[Error]
The text was updated successfully, but these errors were encountered: