Repository navigation
Test failure baseservices\\exceptions\\stackoverflow\\stackoverflowtester\\stackoverflowtester.cmd #84911
Description
Run: runtime-coreclr jitstress-isas-x86 20230415.1
Failed test:
coreclr windows x86 Checked jitstress_isas_nohwintrinsic @ Windows.10.Amd64.Open
- baseservices\\exceptions\\stackoverflow\\stackoverflowtester\\stackoverflowtester.cmd
Error message:
cmdLine:C:\h\w\B25509AE\w\A1800911\e\baseservices\exceptions\stackoverflow\stackoverflowtester\stackoverflowtester.cmd Timed Out (timeout in milliseconds: 1800000 from variable __TestTimeout, start: 4/15/2023 9:38:05 PM, end: 4/15/2023 10:08:05 PM)
Return code: -100
Raw output file: C:\h\w\B25509AE\w\A1800911\uploads\Reports\baseservices.exceptions\stackoverflow\stackoverflowtester\stackoverflowtester.output.txt
Raw output:
BEGIN EXECUTION
"C:\h\w\B25509AE\p\corerun.exe" -p "System.Reflection.Metadata.MetadataUpdater.IsSupported=false" -p "System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization=true" stackoverflowtester.dll
Running stackoverflow test(smallframe main)
"Stack overflow."
"Repeat 43042 times:"
"--------------------------------"
" at TestStackOverflow.Program.InfiniteRecursionB()"
" at TestStackOverflow.Program.InfiniteRecursionA()"
" at TestStackOverflow.Program.InfiniteRecursionC()"
"--------------------------------"
" at TestStackOverflow.Program.InfiniteRecursionB()"
" at TestStackOverflow.Program.InfiniteRecursionA()"
" at TestStackOverflow.Program.Test(Boolean)"
" at TestStackOverflow.Program.Main(System.String[])"
cmdLine:C:\h\w\B25509AE\w\A1800911\e\baseservices\exceptions\stackoverflow\stackoverflowtester\stackoverflowtester.cmd Timed Out (timeout in milliseconds: 1800000 from variable __TestTimeout, start: 4/15/2023 9:38:05 PM, end: 4/15/2023 10:08:05 PM)
Invoking: C:\Program Files (x86)\Windows Kits\10\Debuggers\x86\cdb.exe -c "$<C:\h\w\B25509AE\t\tmpofmm5c.tmp" -z "C:\cores\crashdump_3180.dmp"
stdout:
Microsoft (R) Windows Debugger Version 10.0.18362.1 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\cores\crashdump_3180.dmp]
User Mini Dump File with Full Memory: Only application data is available
************* Path validation summary **************
Response Time (ms) Location
OK C:\h\w\B25509AE\p\PDB
Symbol search path is: C:\h\w\B25509AE\p\PDB
Executable search path is:
Windows 10 Version 14393 MP (4 procs) Free x86 compatible
Product: Server, suite: TerminalServer DataCenter SingleUserTS
10.0.14393.5125 (rs1_release.220429-1732)
Machine Name:
Debug session time: Sat Apr 15 22:08:05.000 2023 (UTC + 0:00)
System Uptime: 0 days 0:47:51.988
Process Uptime: 0 days 0:29:54.000
ERROR: Reload failure, partially initialized target
WaitForEvent failed, HRESULT 0x8000FFFF
Catastrophic failure
When WaitForEvent fails on dump files the current state is not displayed.
If you are having symbol problems you will need to restart the debugger
after you correct the symbol path. .restart can also be used.
?:???> cdb: Reading initial command '$<C:\h\w\B25509AE\t\tmpofmm5c.tmp'
?:???> .load C:\Users\runner.dotnet\sos\sos.dll
WARNING: The debugger does not have a current process or thread
WARNING: Many commands will not work
?:???> ~*k
WARNING: The debugger does not have a current process or thread
WARNING: Many commands will not work
^ Illegal thread error in '~*k'
?:???> !clrstack -f -all
WARNING: The debugger does not have a current process or thread
WARNING: Many commands will not work
Extension called without current PC
SOS does not support the current target architecture '' (0x0000). A 32 bit target may require a 32 bit debugger or vice versa. In general, try to use the same bitness for the debugger and target process.
?:???> q
WARNING: The debugger does not have a current process or thread
WARNING: Many commands will not work
quit:
NatVis script unloaded from 'C:\Program Files (x86)\Windows Kits\10\Debuggers\x86\Visualizers\atlmfc.natvis'
NatVis script unloaded from 'C:\Program Files (x86)\Windows Kits\10\Debuggers\x86\Visualizers\concurrency.natvis'
NatVis script unloaded from 'C:\Program Files (x86)\Windows Kits\10\Debuggers\x86\Visualizers\cpp_rest.natvis'
NatVis script unloaded fr
Stack trace
at baseservices_exceptions._stackoverflow_stackoverflowtester_stackoverflowtester_._stackoverflow_stackoverflowtester_stackoverflowtester_cmd()
at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
at System.Reflection.MethodInvoker.Invoke(Object obj, IntPtr* args, BindingFlags invokeAttr)
Known Issue Error Message
Fill the error message using step by step known issues guidance.
{
"ErrorMessage": ["stackoverflowtester","Timed Out"],
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}Known issue validation
Build: 🔎
Result validation:
Validation performed at: 7/28/2024 3:43:37 AM UTC
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 0 | 18 | 45 |
Metadata
Metadata
Assignees
Labels
CLR JIT issues involving JIT internal stress modesUse this to report build issues in the .NET Helix tabWork that is critical for the release, but we could probably ship withoutBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'Blocking optional rolling runsThe test is disabled in source code against the issueThere is an active PR which will close this issue when it is mergedLinux OS (any supported distro)
Activity
BruceForstall commentedon Apr 17, 2023
Another stackoverflowtester failure @janvorli
v-wenyuxu commentedon May 6, 2023
Failed again in: runtime-coreclr pgostress 20230428.1
Failed test:
Error message:
v-wenyuxu commentedon May 15, 2023
Failed again in: runtime-coreclr pgostress 20230512.1
Failed tests:
�Error message:
�Stack trace:
v-wenyuxu commentedon May 24, 2023
Failed again in: runtime-coreclr jitstress 20230522.1
Failed tests:
Error message:
Stack trace:
v-wenyuxu commentedon Jun 5, 2023
Failed again in: runtime-coreclr pgostress 20230602.1
Failed test:
Error message:
v-wenyuxu commentedon Jun 12, 2023
Failed again in: runtime-coreclr pgostress 20230609.1
Failed tests:
Error message:
Stack trace:
33 remaining items
Disable stackoverflowtester test for osx-x64 (#106411)
janvorli commentedon Aug 15, 2024
I am taking over this issue as I've just got back from my vacation. The stack overflow tester app fails with SIGSEGV instead of stack overflow in the failure cases, so it seems like the stack overflow detection doesn't work in some edge cases.
janvorli commentedon Aug 15, 2024
It seems that in all the cases, it occurs when stack overflow was triggered on the main thread without stack probing.
janvorli commentedon Aug 15, 2024
The issue occurs with spmi only.
jakobbotsch commentedon Aug 15, 2024
@janvorli All the failures in the table above should be from innerloop pipelines. E.g. here's one from a rolling runtime run with an osx-x64 failure: https://dev.azure.com/dnceng-public/public/_build/results?buildId=772131&view=results
janvorli commentedon Aug 15, 2024
osx-x64 is a different story. It hangs waiting for the child process exit (the child exits, but the wait handle is never signaled). We had the same problem with unhandled exception tests on osx-x64. It is not clear why that happens yet.
The linux though is caused by a bug in the sigsegv handler and I am about to send a PR with a fix.
Fix stack overflow handling with SuperPMI
Fix stack overflow handling with SuperPMI
Fix stack overflow handling with SuperPMI (dotnet#106495)
Fix stack overflow handling with SuperPMI (dotnet#106495)