-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Proxy exitJS synchronously, just like the low level proc_exit #18770
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
tlively
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Won't synchronous proxying make the worker wait forever? Or is that not a problem because it will be terminated by the main thread during the exit. Does this work both with and without EXIT_RUNTIME?
Yes, when you call exit() from a worker it will then block forever until it gets terminated. This was already true for (i.e. proc_exit was already proxied fully synchronously). |
Also, convert test_html5_core. These are the two tests that otherwise will fail when #18770 lands.
This simplifies the code and reduces code size. Add testing of both `exit` and `_exit` in test_pthread_exit_runtime.
These are the two tests otherwise starting failing with #18770. The reason is that.
These are the two tests otherwise starting failing with #18770. The reason is that.
These are the two tests otherwise starting failing with #18770. The reason is that.
This simplifies the code and reduces code size. Allows removal of separate
exitOnMainThread function.
Add testing of both
exitand_exitin test_pthread_exit_runtime.