emrun --kill_exit 4.0.16 regression #25654
Description
Hello,
I just updated EmSDK from 4.0.13 to 4.0.18 and noticed that CI tests for WASM in my project failed on timeout.
I have Catch2 based unittests, which passed successfully.
CI failed on timeout.
I launch unittest using following cmdline:
emrun --browser chrome --hostname=localhost --kill_exit --browser_args="--enable-experimental-webassembly-features --headless --remote-debugging-port=0 --disable-gpu --disable-software-rasterizer" <pathtotest.html>
They fail when test code is finished on exit.
If I add --verbose for emrun, then it says:
Web page has quit with a call to exit() with return code 0. Shutting down web server. Pass --serve-after-exit to keep serving even after the page terminates with exit().
Web server loop done.
When I try to interrupt it using Ctrl+C, then:
Traceback (most recent call last):
File "/Users/dev/Documents/Project/ThirdParty/EmSDK/Source/upstream/emscripten/emrun.py", line 1896, in <module>
sys.exit(main(sys.argv[1:]))
~~~~^^^^^^^^^^^^^^
File "/Users/dev/Documents/Project/ThirdParty/EmSDK/Source/upstream/emscripten/emrun.py", line 1888, in main
returncode = run(args)
File "/Users/dev/Documents/Project/ThirdParty/EmSDK/Source/upstream/emscripten/emrun.py", line 1861, in run
httpd.server_close()
~~~~~~~~~~~~~~~~~~^^
File "/Users/dev/Documents/Project/ThirdParty/EmSDK/Source/python/3.13.3_64bit/lib/python3.13/socketserver.py", line 715, in server_close
self._threads.join()
~~~~~~~~~~~~~~~~~~^^
File "/Users/dev/Documents/Project/ThirdParty/EmSDK/Source/python/3.13.3_64bit/lib/python3.13/socketserver.py", line 661, in join
thread.join()
~~~~~~~~~~~^^
File "/Users/dev/Documents/Project/ThirdParty/EmSDK/Source/python/3.13.3_64bit/lib/python3.13/threading.py", line 1092, in join
self._handle.join(timeout)
Note: I compared behaviour between different EmSDK versions and this problem didn't exist on 4.0.15 and 4.0.16 introduced it.
I have the same issue across different desktop platforms: Windows 11, Linux (Ubuntu 24), MacOS 26.0.1.
I wonder if it is known issue.
I'm not familiar with Python debugging, but I can test different pre 4.0.16 commits if it necessary.
Let me know if you need more information.
Regards,
Kostiantyn