emscripten failed to load in iOS Safari\Chrome if Worker Threads are greater than 10. (macOS is OK) #20377
Replies: 3 comments 1 reply
-
More info: when I compiled with Optimizations Flags, then I can raise up a 20 Worker Threads, I need to raise up at least 40 Worker Threads. |
Beta Was this translation helpful? Give feedback.
-
Hi, glad to hear you :) The WASM and its DATA are about 50M, so it is might explain a Memory issue. |
Beta Was this translation helpful? Give feedback.
-
In iOS (version 16) Safari\Chrome It seems that there is no limitation on number of Worker Threads, but there is limitation on memory size - the max size is 1.5G . |
Beta Was this translation helpful? Give feedback.
-
My emscripten app is failed to load in iOS 16\17 Safari\Chrome if Worker Threads are greater than 10 (macOS is OK).
I would be glad if anybody knows about any workaround for this.
here are the emscripten flags that I use to build my App:
-s ALLOW_TABLE_GROWTH -s WASM_BIGINT -s EXPORTED_RUNTIME_METHODS=ccall,cwrap,addFunction -s EXPORTED_FUNCTIONS=_main -g -gsplit-dwarf -gdwarf-5 -gpubnames --bind -s USE_PTHREADS -s ALLOW_MEMORY_GROWTH=1 -s ASSERTIONS -s FETCH -s NO_DISABLE_EXCEPTION_CATCHING -s TEXTDECODER=0 -lidbfs.js -s PTHREAD_POOL_SIZE=15 -s ERROR_ON_WASM_CHANGES_AFTER_LINK -s REVERSE_DEPS=all -s STACK_SIZE=1mb -s DEFAULT_PTHREAD_STACK_SIZE=1mb -s ALLOW_BLOCKING_ON_MAIN_THREAD=1 -s PTHREAD_POOL_SIZE_STRICT=2
Beta Was this translation helpful? Give feedback.
All reactions