[browser][MT] fix thread creation race with finalizer #100778
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…p, not lazily - make loaderHelpers.loadingWorkers Promise - FinalizerWorks test - drop finalizerThreadStartDelayMs - drop is_thread_available - fix browser-threads sample
|
Tagging subscribers to 'arch-wasm': @lewing |
This was referenced Apr 8, 2024
ilonatommy
approved these changes
Apr 9, 2024
31 tasks
matouskozak
pushed a commit
to matouskozak/runtime
that referenced
this pull request
Apr 30, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
mono_wasm_init_finalizer_threadimmediately during startup, not lazilyloaderHelpers.loadingWorkersPromiseFinalizerWorkstestfinalizerThreadStartDelayMsis_thread_availablebrowser-threadssample