Repository navigation
System.AccessViolationException in System.Threading.Tasks.Tests Work Item #130595
Copy link
Copy link
Closed
Labels
JitStressCLR JIT issues involving JIT internal stress modesCLR JIT issues involving JIT internal stress modesarea-CodeGen-coreclrCLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMICLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMIblocking-clean-ci-optionalBlocking optional rolling runsBlocking optional rolling runs
Description
Failed in: runtime-coreclr libraries-jitstress2-jitstressregs 20260711.1
Failed tests:
net11.0-windows-Release-arm64-jitstress2_jitstressregs0x80-Windows.11.Arm64.Open
- System.Threading.Tasks.Tests Work Item
Error message:
Fatal error.
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Stack trace:
at System.Threading.Tasks.Tests.AsyncProfilerTests+<>c__DisplayClass84_0.<CollectEventsAsync>b__0()
at System.Runtime.CompilerServices.AsyncProfiler+ContinuationWrapper.Continuation_Wrapper_1(System.Runtime.CompilerServices.Continuation, Byte ByRef)
Repeated 2 times:
--------------------------------
at System.Runtime.CompilerServices.AsyncHelpers+RuntimeAsyncTask`1[[System.Threading.Tasks.VoidTaskResult, System.Private.CoreLib, Version=11.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].InstrumentedDispatchContinuations(Flags)
at System.Runtime.CompilerServices.AsyncHelpers+RuntimeAsyncTask`1[[System.Threading.Tasks.VoidTaskResult, System.Private.CoreLib, Version=11.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].DispatchContinuations()
at System.Threading.Tasks.Task.RunContinuations(System.Object)
at System.Threading.Tasks.Task`1[[System.Threading.Tasks.VoidTaskResult, System.Private.CoreLib, Version=11.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].TrySetResult(System.Threading.Tasks.VoidTaskResult)
--------------------------------
at System.Runtime.CompilerServices.AsyncHelpers+RuntimeAsyncTask`1[[System.Threading.Tasks.VoidTaskResult, System.Private.CoreLib, Version=11.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].InstrumentedDispatchContinuations(Flags)
at System.Runtime.CompilerServices.AsyncHelpers+RuntimeAsyncTask`1[[System.Threading.Tasks.VoidTaskResult, System.Private.CoreLib, Version=11.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].DispatchContinuations()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading.PortableThreadPool+WorkerThread.WorkerDoWork(System.Threading.PortableThreadPool)
at System.Threading.PortableThreadPool+WorkerThread.WorkerThreadStart()
at System.Threading.Thread.StartCallback(System.Threading.Thread*)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
JitStressCLR JIT issues involving JIT internal stress modesCLR JIT issues involving JIT internal stress modesarea-CodeGen-coreclrCLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMICLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMIblocking-clean-ci-optionalBlocking optional rolling runsBlocking optional rolling runs
Activity
dotnet-policy-service commentedon Jul 13, 2026
Tagging subscribers to this area: @JulieLeeMSFT, @VSadov
See info in area-owners.md if you want to be subscribed.
dotnet-policy-service commentedon Jul 13, 2026
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.
jakobbotsch commentedon Jul 13, 2026
I suspect this was fixed already via #130536.
jakobbotsch commentedon Jul 14, 2026
Looked at the dump and the crash is right around the same code as in #130212:
Indeed I validated with Copilot that we CSE'd the thread base and reloaded it from the continuation.