-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
[browser] mono_exit improvements #88387
Conversation
Tagging subscribers to 'arch-wasm': @lewing Issue Details
|
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
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.
Looks fine other than comments
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
6aa209b
to
021af3f
Compare
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
# Conflicts: # src/mono/wasm/runtime/http.ts # src/mono/wasm/runtime/web-socket.ts
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm |
No commit pushedDate could be found for PR 88387 in repo dotnet/runtime |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm |
No commit pushedDate could be found for PR 88387 in repo dotnet/runtime |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
mono_wasm_exit
frommono_exit
shutting_down_inited
and then join all mono threadsassert_runtime_running
to many entry pointsonExit
withAssertAfterExit
andassertAfterExit
which is default true for shell/nodetest-main.js
mono_assert
to abort the program and introducedmono_check
alternative which just throws exception.browser-shutdown
sample from @kg's PRabort_startup
withmono_exit
Alternative to #87043