I have seen several cases of crash in the tracing/runtimeeventsource/nativeruntimeeventsource/nativeruntimeeventsource on Linux in InterpThreadContext destructor in the CI. The destructor is called from Thread::OnThreadTerminate. In the case when I have looked into, it was called from the Thread::CleanupDetachedThreads. The thread object contained reasonable information (e.g. the m_OSThreadId was a value that made sense w.r.t. the other thread's values.
The state was as follows:
m_StateNC : 0x100 ( TSNC_ExistInThreadStore )
m_State : 0x31220 (TS_LegalToJoin | TS_Background | TS_WeOwn | TS_ReportDead | TS_FullyInitialized)
The InterpThreadContext struct content was garbage and the pointer itself didn't seem to be right (!maddress said it is pointing to a block marked as "Stack"). However, the pointer is null-ed in Thread constructor and only set at one place to a value obtained by new operator.
Known Issue Error Message
Fill the error message using step by step known issues guidance.
{
"ErrorMessage": "",
"ErrorPattern": "nativeruntimeeventsource.*Segmentation fault",
"BuildRetry": false,
"ExcludeConsoleLog": false
}Known issue validation
Build: 🔎
Result validation: ⚠️ Validation could not be done without an Azure DevOps build URL on the issue. Please add it to the "Build: 🔎" line.
Validation performed at: 12/21/2025 3:20:21 PM UTC
Report
Summary
| 24-Hour Hit Count |
7-Day Hit Count |
1-Month Count |
| 0 |
0 |
0 |
I have seen several cases of crash in the tracing/runtimeeventsource/nativeruntimeeventsource/nativeruntimeeventsource on Linux in
InterpThreadContextdestructor in the CI. The destructor is called fromThread::OnThreadTerminate. In the case when I have looked into, it was called from theThread::CleanupDetachedThreads. The thread object contained reasonable information (e.g. them_OSThreadIdwas a value that made sense w.r.t. the other thread's values.The state was as follows:
The
InterpThreadContextstruct content was garbage and the pointer itself didn't seem to be right (!maddress said it is pointing to a block marked as "Stack"). However, the pointer is null-ed in Thread constructor and only set at one place to a value obtained bynewoperator.Known Issue Error Message
Fill the error message using step by step known issues guidance.
{ "ErrorMessage": "", "ErrorPattern": "nativeruntimeeventsource.*Segmentation fault", "BuildRetry": false, "ExcludeConsoleLog": false }Known issue validation
Build: 🔎⚠️ Validation could not be done without an Azure DevOps build URL on the issue. Please add it to the "Build: 🔎" line.
Result validation:
Validation performed at: 12/21/2025 3:20:21 PM UTC
Report
Summary