Emrun does not receive the runtime exit

[JD31]

Please include the following in your bug report:

Version of emscripten/emsdk:
4.0.19

Command line:
python.exe "../../emrun.py" "--browser" "chrome" "--dump_out_directory" "../../screenshots/" "--browser-args="--start-maximized --enable-unsafe-webgpu --ignore-gpu-blocklist --disable-domain-blocking-for-3d-apis --disable-dawn-features=use_dxc --disable-backgrounding-occluded-windows"" "Renderer_integration.html"

I have several Catch2 tests that used to work correctly with emsdk 3.1.64.
Since I moved to 4.0.19 all tests get stuck. It seems that the runtime is exited but that emrun does not receive the information.
I am exiting with emscripten_force_exit.
Is there something new I need to do for emrun to catch the end of the test ?

For more details :
I use the link options "--emrun -s EXIT_RUNTIME=1 -sPTHREAD_POOL_SIZE=4".
All autotest that does not use a render loop correctly exists emrun.
The graphic tests that uses a render loop (emscripten_set_main_loop_arg) does not exit emrun even after call to 'emscripten_cancel_main_loop' followed by 'emscripten_force_exit'. Note that in this case, the application is no more responding thus it seems that the runtime exited but that this signal does not reach emrun.

[JD31]

I am now able to propagate correctly the exit to emrun by adding the following :

                EM_ASM({
                    var http = new XMLHttpRequest();
                    http.open("POST", "stdio.html", false);
                    http.send("^exit^" + $0);
                    try { close(); } catch(e) {}
                }, Test::exitCode);

I copied this code from 'emrun_postjs.js'.
But I don't understand why it is not called in the first place...