-
Notifications
You must be signed in to change notification settings - Fork 5.4k
Closed
Labels
JitStressCLR JIT issues involving JIT internal stress modesCLR JIT issues involving JIT internal stress modesarch-x86area-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 runsos-windows
Milestone
Description
Failed in: runtime-coreclr jitstress-random 20251026.1
Failed tests:
coreclr windows x86 Checked jitstress_random_1 @ Windows.10.Amd64.Open
- JIT/Directed/pinvoke/tail_pinvoke/tail_pinvoke.cmd
coreclr windows x86 Checked jitstress_random_2 @ Windows.10.Amd64.Open
- JIT/Directed/pinvoke/tail_pinvoke/tail_pinvoke.cmd
Error message:
Assert failure(PID 3352 [0x00000d18], Thread: 836 [0x0344]): Assertion failed '!tailCall' in 'JitTest.Test:__GetMenuString(nuint,uint,System.Text.StringBuilder,int,uint):int' during 'Linear scan register alloc' (IL size 8; hash 0x1b7690c9; FullOpts)
File: D:�_work1ssrccoreclrjitcodegencommon.cpp:2532
Image: C:hwA593093Apcorerun.exe
Return code: 1
Raw output file: C:hwA593093AwAE4D09E7uploadspinvoke ail_pinvokeoutput.txt
Raw output:
BEGIN EXECUTION
"C:hwA593093Apcorerun.exe" -p "System.Reflection.Metadata.MetadataUpdater.IsSupported=false" -p "System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization=true" tail_pinvoke.dll
Expected: 100
Actual: -1073740286
END EXECUTION - FAILED
FAILED
Test failed. Trying to see if dump file was created in C:cores since 10/26/2025 7:35:50 PM
Processing C:corescorerun.exe.3352.dmp
Invoking: C:Program Files (x86)Windows Kits10Debuggers�cdb.exe -c "$<C:hwA593093A mpo4cirf.tmp" -z "C:corescorerun.exe.3352.dmp"
stdout:
Microsoft (R) Windows Debugger Version 10.0.18362.1 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:corescorerun.exe.3352.dmp]
User Mini Dump File with Full Memory: Only application data is available
************* Path validation summary **************
Response Time (ms) Location
OK C:hwA593093ApPDB
Symbol search path is: C:hwA593093ApPDB
Executable search path is:
Windows 10 Version 14393 MP (4 procs) Free x86 compatible
Product: Server, suite: TerminalServer DataCenter SingleUserTS
10.0.14393.6343 (rs1_release.230913-1727)
Machine Name:
Debug session time: Sun Oct 26 19:35:57.000 2025 (UTC + 0:00)
System Uptime: 0 days 0:04:13.702
Process Uptime: 0 days 0:00:07.000
...............................
************* Symbol Loading Error Summary **************
Module name Error
ntdll The system cannot find the file specified
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(d18.344): Unknown exception - code c0000602 (first/second chance not available)
For analysis of this file, run !analyze -v
*** WARNING: Unable to verify checksum for coreclr.dll
eax=00a39d18 ebx=00000000 ecx=00000000 edx=00000000 esi=00a39cc8 edi=00a39d18
eip=7364e962 esp=00a39ffc ebp=00a3b090 iopl=0 nv up ei pl nz ac po nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000212
coreclr!FailFastOnAssert+0x21:
7364e962 5e pop esi
0:000> cdb: Reading initial command '$<C:hwA593093A mpo4cirf.tmp'
0:000> .cordll -lp "C:hwA593093Ap"
The call to LoadLibrary(sos) failed, Win32 error 0n2
"The system cannot find the file specified."
Please check your debugger configuration and/or network access.
CLR DLL status: Loaded DLL C:hwA593093Apmscordaccore.dll
0:000> .load C:Users
unner.dotnetsossos.dll
0:000> ~*k
. 0 Id: d18.344 Suspend: 0 Teb: 02ffd000 Unfrozen
ChildEBP RetAddr
00a3a008 7364f784 coreclr!FailFastOnAssert+0x21
00a3b090 7383f145 coreclr!_DbgBreakCheck+0x2f5
*** WARNING: Unable to verify checksum for clrjit.dll
00a3b0fc 71b524b6 coreclr!CEEInfo::doAssert+0x65
00a3d12c 71b2e198 clrjit!assertAbort+0xe2
00a3d144 71c4269d clrjit!CodeGenInterface::genGetGSCookieTempRegs+0x20
00a3d1b8 71c37888 clrjit!LinearScan::buildIntervals<1>+0x99c
00a3d1e4 71b3857b clrjit!LinearScan::doLinearScan+0x58
(Inline) -------- clrjit!Compiler::compCompile::__l2::<lambda_6>::operator()+0x1b
00a3d1f0 71c797d8 clrjit!ActionPhase<`Compiler::compCompile'::`2'::<lambda_6> >::DoPhase+0x1b
00a3d224 71b3cb72 clrjit!Phase::Run+0x38
(Inline) -------- clrjit!DoPhase+0x2b
00a3d6d4 71b3e10c clrjit!Compiler::compCompile+0xabb
00a
Stack trace:
at TestLibrary.OutOfProcessTest.RunOutOfProcessTest(String assemblyPath, String testPathPrefix)
at Program.<<Main>$>g__TestExecutor232|0_233(StreamWriter tempLogSw, StreamWriter statsCsvSw, <>c__DisplayClass0_0&)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
JitStressCLR JIT issues involving JIT internal stress modesCLR JIT issues involving JIT internal stress modesarch-x86area-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 runsos-windows