Repository navigation
AF: *(_UNCHECKED_OBJECTREF *)handle == NULL (HndCreateHandle called by getJitHandleForObject) #117138
Copy link
Copy link
Open
Labels
GCStressKnown Build ErrorUse this to report build issues in the .NET Helix tabUse this to report build issues in the .NET Helix tabarea-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-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'blocking-clean-ci-optionalBlocking optional rolling runsBlocking optional rolling runs
Milestone
Description
Failed in: runtime-coreclr gcstress-extra 20250629.1
Failed tests:
coreclr osx arm64 Checked gcstress0xc_disabler2r @ OSX.13.Arm64.Open
- JIT/Regression/JitBlue/DevDiv_461649/DevDiv_461649/DevDiv_461649.cmd
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1081377&view=results
Build error leg or test failing:
Error Message
Fill the error message using step by step known issues guidance.
{
"ErrorMessage": "*(_UNCHECKED_OBJECTREF *)handle == NULL",
"BuildRetry": false,
"ExcludeConsoleLog": false
}Known issue validation
Build: 🔎
Result validation:
Validation performed at: 9/28/2025 6:05:32 PM UTC
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 0 | 9 | 24 |
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
GCStressKnown Build ErrorUse this to report build issues in the .NET Helix tabUse this to report build issues in the .NET Helix tabarea-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-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'blocking-clean-ci-optionalBlocking optional rolling runsBlocking optional rolling runs
Activity
amanasifkhalid commentedon Jul 28, 2025
This hasn't hit in the last few runs. Removing blocking-optional tag.
16 remaining items
EgorBo commentedon Mar 8, 2026
Managed to make a repro out of your idea that fairly quickly hits exactly the same assert (in a matter of seconds):
or some other runs hit:
Repro.cs (static readonly array (non-frozen object) + length access generates jit-time handles) + a thread with GC.Collect (poor man's GCStress) + a thread with GC pressure + several config knobs:
and if the repro is spinned in a loop:
EgorBo commentedon Mar 8, 2026
Can confirm
GCX_COOPinsidevirtual ~CEEInfo()makes bug go awayEgorBo commentedon Mar 9, 2026
@jkotas for
It seems we call DestroyHandle from many places and it's not trivial to trace what GC modes are used for that (especially for various destructors), can we just switch to COOP inside
DestroyHandleCommonitself? or it's an overhead for cases where it's already in COOP?My AI-driven attempt to use COOP in all callers: 6cedb0c
jkotas commentedon Mar 9, 2026
Yes, for the GCHandle FCalls in particular. I expect that the extra GCX_COOP will show up in micro-benchmarks.
Also, I suspect we may need to do a bit of refactoring around some of the destructors. They may be called in a place where it is not possible to switch GC modes.
Is this all? It does not look too bad.
JulieLeeMSFT commentedon May 1, 2026
Failed in:
Console Log: Console Log
Source: runtime-coreclr libraries-pgo / net11.0-linux-Release-x64-defaultpgo-AzureLinux.3.Amd64.Open / System.Text.Json.Tests
Failed tests:
[ci-scan] Skip SocketBlockingModeTransitionTests.ConnectAsync_WithBuf…
JulieLeeMSFT commentedon Jul 9, 2026
Failed in (1):
Console Log: Console Log
Source: runtime-coreclr libraries-pgo / net11.0-windows-Release-x64-jitosr_stress-Windows.10.Amd64.Open / System.Runtime.Numerics.Tests
Failed tests:
Error Message:
VincentBu commentedon Jul 13, 2026
Failed in: runtime-coreclr libraries-jitstress2-jitstressregs 20260711.1
Failed tests:
Error message:
[ci-scan] Skip SocketBlockingModeTransitionTests.ConnectAsync_WithBuf…
hez2010 commentedon Aug 27, 2026
I just hit this in pri 0 tests without stress.
See https://dev.azure.com/dnceng-public/public/_build/results?buildId=1570019&view=logs&jobId=60eb2ed7-6b32-5072-53a3-69713626aad6&j=60eb2ed7-6b32-5072-53a3-69713626aad6&t=ecb1647b-6a6c-5896-e385-2c6b24adf079
VincentBu commentedon Sep 8, 2026
Failed in: runtime-coreclr gcstress-extra 20260906.1
Failed tests:
Error message:
Stack trace: