-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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][MT] withDumpThreadsOnNonZeroExit #98052
Conversation
- pass more of it into RuntimeAPI.runtimeBuildInfo - move MONO_LOG_LEVEL, MONO_LOG_MASK, DOTNET_DebugWriteToStdErr, MONO_SLEEP_ABORT_LIMIT to test-main.js - implement dumpThreadsOnExit and withDumpThreadsOnExit - implement mono_native_thread_set_name via mono_wasm_pthread_set_name - implement mono_native_thread_create - renamed set_thread_prefix
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsI hope this will help to troubleshoot the GC deadlocks
|
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
Co-authored-by: Marek Fišera <mara@neptuo.com>
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
…ara/runtime into browser_mt_thread_names
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
I filled #98086 Unfortunately the CI is not in great shape today. At least |
I hope this will help to troubleshoot the GC deadlocks
mono_jit_cleanup
only when exit code is zerodumpThreadsOnNonZeroExit
andwithDumpThreadsOnNonZeroExit
, when exit code is not zeroEmscriptenBuildOptions
into separate objectRuntimeAPI.runtimeBuildInfo
MONO_LOG_LEVEL
,MONO_LOG_MASK
,DOTNET_DebugWriteToStdErr
,MONO_SLEEP_ABORT_LIMIT
totest-main.js
mono_native_thread_set_name
viamono_wasm_pthread_set_name
mono_native_thread_create
set_thread_prefix