Jan Kotas

> @jkotas do these symptoms ring any bells for you as to what may be happening? I think that that the most likely explanation of these symptoms is that the...

> has anything recently changed in the implementation or around inlining decisions here? If my theory above is correct, the problem was likely triggered by #99183 .

The equivalent check in VM does use VolatileLoad: https://github.com/dotnet/runtime/blob/main/src/coreclr/vm/methodtable.h#L461

> I'm perplexed at how this can happen. Any insight? This is a bug in TransationManager. `TransationManager.DefaultTimeOut` is a global static. What can happen is: - One thread is running...

This bug was introduced in #71703. cc @imcarolwang @HongGit

Stacktrace: ``` DbgAssertDialog CrstBase::PreEnter() CrstBase::Enter(CrstBase::NoLevelCheckFlag) TableCacheMissOnFree(HandleTable*, HandleTypeCache*, unsigned int, OBJECTHANDLE__*) HndDestroyHandle(HandleTable*, unsigned int, OBJECTHANDLE__*) GetThreadLocalStaticBase(TLSIndex) Thread::GetStaticFieldAddress(FieldDesc*) InvokeUtil::GetFieldValue(FieldDesc*, TypeHandle, OBJECTREF*, TypeHandle, bool*) RuntimeFieldHandle::GetValue(ReflectFieldObject*, Object*, ReflectClassBaseObject*, ReflectClassBaseObject*, bool*) System.Reflection.FieldAccessor.GetValue(System.Object) ```

Looks like a regression introduced by the statics rewrite. @davidwrighton Could you please take a look?

Timed out in #113676 on arm64: - The main thread of the child process is in the middle of ExitProcess and trying to acquire native heap lock: ``` ntdll!RtlAcquireSRWLockExclusive+0x34 [minkernel\ntos\rtl\srwlock.c...

> when jumping locally between Windows and WSL, you need to keep nuking You can work around this by installing the right .NET SDK in a global location on both...

`Expected: ".NET Long Runni"` is very generic pattern that can match number of unrelated issues. I have updated it to be make it more specific.