Jan Kotas

> How that Design namespace issues can be hidden from trim warnings? Make sure that the code from Design namespace is not getting rooted and that it gets trimmed in...

The failure was most likely triggered by Linux kernel update, docker container update or test infra update. These updates are rolled out regularly in the background. I do not think...

cc @janvorli

This is crashing in new EH: ``` 0b 00000032`5797bd90 00007ffa`cd1a213c ntdll!RtlDispatchException+0x200 [minkernel\ntos\rtl\arm64\exdsptch.c @ 720] 0c 00000032`5797c3d0 00007ffa`c8ef8274 ntdll!RtlRaiseException+0xbc [minkernel\ntos\rtl\arm64\raise.c @ 123] 0d 00000032`5797c8b0 00007ffa`756d4be8 KERNELBASE!RaiseException+0x54 [minkernel\kernelbase\xcpt.c @ 936] 0e 00000032`5797c960...

Either way, CI does not hit this anymore, so the issue can be closed.

Failed again in https://dev.azure.com/dnceng-public/public/_build/results?buildId=655183&view=ms.vss-test-web.build-test-results-tab&runId=16217960&resultId=100465&paneView=debug with the same stacktrace as https://github.com/dotnet/runtime/issues/100114#issuecomment-2014220793

Ah ok, I have not realized that this is the new callstack for unhandled exception. I agree that it looks like a profiler test issue. We would need a crash...

Based on the dump, the child process exit code is 0: ``` 0:000> !do 000001f8`7080afc8 Name: System.Diagnostics.Process MethodTable: 00007ffbf63dca00 ... 00007ffbf5c4f900 40000dd d8 System.Int32 1 instance 0 _exitCode ... ```...

Missing `volatile` that I have added in https://github.com/dotnet/runtime/pull/101607 can explain failures with these symptoms. I suspect that my change is not going to fix the failures. The test has been...

A good question to ask is why this test and why arm64 only. It all points to bug(s) related to arm64 weaker memory model in the test code or in...