Repository navigation
Closed
Closed
Copy link
Labels
JitStressCLR JIT issues involving JIT internal stress modesCLR JIT issues involving JIT internal stress modesarch-arm32area-System.Threadingos-linuxLinux OS (any supported distro)Linux OS (any supported distro)
Milestone
Description
Failed in: runtime-coreclr jitstress 20251108.1
Failed tests:
coreclr linux arm Checked jitstress1 @ (Debian.13.Arm32.Open)Ubuntu.2204.ArmArch.Open@mcr.microsoft.com/dotnet-buildtools/prereqs:debian-13-helix-arm32v7
- GC/API/GC/GetTotalAllocatedBytes/GetTotalAllocatedBytes.cmd
Error message:
Return code: 1
Raw output file: /root/helix/work/workitem/uploads/API/GC/GetTotalAllocatedBytes/output.txt
Raw output:
BEGIN EXECUTION
/root/helix/work/correlation/corerun -p System.Reflection.Metadata.MetadataUpdater.IsSupported=false -p System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization=true GetTotalAllocatedBytes.dll ''
System.AggregateException: One or more errors occurred. (Exception of type 'System.OutOfMemoryException' was thrown.)
---> System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
at System.Threading.Thread.StartCore()
at System.Threading.Thread.Start(Boolean captureContext)
at Test_GetTotalAllocatedBytes.<>c__DisplayClass10_0.<TestAnotherThread>b__0()
at System.Threading.Tasks.Task.InnerInvoke()
at System.Threading.Tasks.Task.<>c.<.cctor>b__289_0(Object obj)
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
at __GeneratedMainWrapper.Main()
Expected: 100
Actual: 101
END EXECUTION - FAILED
Test failed. Trying to see if dump file was created in /datadisks/disk1/dumps since 11/9/2025 6:07:08 AM
Test Harness Exitcode is : 1
To run the test:
Set up CORE_ROOT and run.
> /root/helix/work/workitem/e/GC/GC/../API/GC/GetTotalAllocatedBytes/GetTotalAllocatedBytes.sh
Stack trace:
at TestLibrary.OutOfProcessTest.RunOutOfProcessTest(String assemblyPath, String testPathPrefix)
at Program.<<Main>$>g__TestExecutor28|0_29(StreamWriter tempLogSw, StreamWriter statsCsvSw, <>c__DisplayClass0_0&)
Known Issue Error Message
Fill the error message using step by step known issues guidance.
{
"ErrorMessage": ["API/GC/GetTotalAllocatedBytes","OutOfMemoryException"],
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}Known issue validation
Build: 🔎
Result validation:
Validation performed at: 12/20/2025 2:13:46 AM UTC
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 2 | 9 | 26 |
Reacted by Copilot
Metadata
Metadata
Labels
JitStressCLR JIT issues involving JIT internal stress modesCLR JIT issues involving JIT internal stress modesarch-arm32area-System.Threadingos-linuxLinux OS (any supported distro)Linux OS (any supported distro)
Activity
dotnet-policy-service commentedon Nov 10, 2025
Tagging subscribers to this area: @mangod9
See info in area-owners.md if you want to be subscribed.
MihuBot commentedon Nov 10, 2025
I'm a bot. Here is a possible related and/or duplicate issue (I may be wrong):
michaellinhq commentedon Feb 15, 2026
Hi, I reviewed 'Test failure: GC/API/GC/GetTotalAllocatedBytes/GetTotalAllocatedBytes.cmd' and can start immediately. I can deliver a first usable version quickly and iterate based on your feedback. If this scope still matches your priority, I can proceed right away.
michaellinhq commentedon Feb 15, 2026
Hi, I reviewed 'Test failure: GC/API/GC/GetTotalAllocatedBytes/GetTotalAllocatedBytes.cmd' and can start immediately. I can deliver a first usable version quickly and iterate based on your feedback. If this scope still matches your priority, I can proceed right away.
VSadov commentedon Apr 29, 2026
1000 quickly created threads could be too many for a 32bit environment.
We should reduce that to 100 on 32bit and reenable the test (if disabled).