Closed carstene1ns closed 3 years ago
We have these for a while, on old and new server, corresponding to each player-js build:
player-js
root@easyrpg ~# ps axww | grep emscripten | tail -n+2 22661 ? S 0:00 /bin/python /var/lib/jenkins/workspace/toolchain-emscripten/emscripten/emsdk-portable/emscripten/incoming/emcc.py -g -O2 --memory-init-file 1 --llvm-lto 1 -v -s WASM=0 -s ASSERTIONS=0 -s NO_EXIT_RUNTIME=1 -s ALLOW_MEMORY_GROWTH=1 -s DEMANGLE_SUPPORT=1 easyrpg-player.bc -o /var/lib/jenkins/play/pr1716/index-pr.html --post-js resources/emscripten/emscripten-post.js --shell-file resources/emscripten/emscripten-shell.html 22664 ? S 0:00 /bin/python /var/lib/jenkins/workspace/toolchain-emscripten/emscripten/emsdk-portable/emscripten/incoming/emcc.py -g -O2 --memory-init-file 1 --llvm-lto 1 -v -s WASM=0 -s ASSERTIONS=0 -s NO_EXIT_RUNTIME=1 -s ALLOW_MEMORY_GROWTH=1 -s DEMANGLE_SUPPORT=1 easyrpg-player.bc -o /var/lib/jenkins/play/pr1716/index-pr.html --post-js resources/emscripten/emscripten-post.js --shell-file resources/emscripten/emscripten-shell.html 22667 ? S 0:00 /bin/python /var/lib/jenkins/workspace/toolchain-emscripten/emscripten/emsdk-portable/emscripten/incoming/emcc.py -g -O2 --memory-init-file 1 --llvm-lto 1 -v -s WASM=0 -s ASSERTIONS=0 -s NO_EXIT_RUNTIME=1 -s ALLOW_MEMORY_GROWTH=1 -s DEMANGLE_SUPPORT=1 easyrpg-player.bc -o /var/lib/jenkins/play/pr1716/index-pr.html --post-js resources/emscripten/emscripten-post.js --shell-file resources/emscripten/emscripten-shell.html 22673 ? S 0:00 /bin/python /var/lib/jenkins/workspace/toolchain-emscripten/emscripten/emsdk-portable/emscripten/incoming/emcc.py -g -O2 --memory-init-file 1 --llvm-lto 1 -v -s WASM=0 -s ASSERTIONS=0 -s NO_EXIT_RUNTIME=1 -s ALLOW_MEMORY_GROWTH=1 -s DEMANGLE_SUPPORT=1 easyrpg-player.bc -o /var/lib/jenkins/play/pr1716/index-pr.html --post-js resources/emscripten/emscripten-post.js --shell-file resources/emscripten/emscripten-shell.html
Manually killing them or rebooting the server works however. I guess they exist since the last toolchain update (for the move to WASM).
Maybe somebody tried to stop emcc the hard way, or some oom triggered it and the python interpreter got stuck like in this one: emscripten-core/emscripten#8013. See also emscripten-core/emscripten#1327.
We have these for a while, on old and new server, corresponding to each
player-js
build:Manually killing them or rebooting the server works however. I guess they exist since the last toolchain update (for the move to WASM).