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
Hello.
I have streamana app installed on my dev server. The problem is the next error that may occur right after livestreaming to the HLS endpoint is started or after some time. This causes livestreaming to stop. Maybe the reason is that I removed a few arguments when building ffmpeg-worker-hls.js. Namely, I removed STACK_SIZE=5MB because of the error: "Attempt to set a non-existent setting: 'STACK_SIZE'". I replaced it with "--stack-size=5242880". Also removed "-O3" and "--closure" (there was an error: "Closure compiler run failed"). My arguments for compiling ffmpeg.js were: EMCC_COMMON_CORE_ARGS = --memory-init-file 0 --stack-size=5242880 -s ABORTING_MALLOC=0 -s WASM_ASYNC_COMPILATION=0 -s ASSERTIONS=1 -s TOTAL_MEMORY=100MB -s DEFAULT_PTHREAD_STACK_SIZE=5MB -s PTHREAD_POOL_SIZE=10 -s ASYNCIFY_STACK_SIZE=65536 --pre-js $(PRE_JS) -o $@
Please help me to fix this bug.
The text was updated successfully, but these errors were encountered:
Hello.$(PRE_JS) -o $ @
I have streamana app installed on my dev server. The problem is the next error that may occur right after livestreaming to the HLS endpoint is started or after some time. This causes livestreaming to stop. Maybe the reason is that I removed a few arguments when building ffmpeg-worker-hls.js. Namely, I removed STACK_SIZE=5MB because of the error: "Attempt to set a non-existent setting: 'STACK_SIZE'". I replaced it with "--stack-size=5242880". Also removed "-O3" and "--closure" (there was an error: "Closure compiler run failed"). My arguments for compiling ffmpeg.js were: EMCC_COMMON_CORE_ARGS = --memory-init-file 0 --stack-size=5242880 -s ABORTING_MALLOC=0 -s WASM_ASYNC_COMPILATION=0 -s ASSERTIONS=1 -s TOTAL_MEMORY=100MB -s DEFAULT_PTHREAD_STACK_SIZE=5MB -s PTHREAD_POOL_SIZE=10 -s ASYNCIFY_STACK_SIZE=65536 --pre-js
Please help me to fix this bug.
The text was updated successfully, but these errors were encountered: