Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[ci-scan] Hang: baseservices/threading/ThreadStateDestroyed

Open Beginner friendly
  • Is something wrong?
#134,679 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
70/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
operating-systems, testing-qa

Research direction

Start with baseservices/threading/ThreadStateDestroyed/ThreadStateDestroyed/ThreadStateDestroyed.cmd and compare its platform conditions with the Apple-platform change referenced in the issue. Run the test on the Windows x86 Checked no_tiered_compilation leg and inspect the test configuration or history. Done means the Windows x86 timeout is handled appropriately and the test passes or is excluded for the affected platform.

Written by the indexing model from the issue text.

Description

area-System.Threading blocking-clean-ci Known Build Error untriaged

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1612477
Build error leg or test failing: coreclr windows x86 Checked no_tiered_compilation @ Windows.10.Amd64.Open-baseservices/threading/ThreadStateDestroyed/ThreadStateDestroyed/ThreadStateDestroyed.cmd
Pull request: https://github.com/dotnet/runtime/pull/134606

KBE authoring guidance (ci-failure-scan)
  • Error Details is for readers. Paste the full exception, stack trace, or build error excerpt so the failure is understandable without opening the raw log.
  • Build Analysis parses only the single JSON block under Error Message.
  • ErrorMessage is a case-sensitive ordinal String.Contains substring copied verbatim from the failing log.
  • Set BuildRetry to true only for a clear infrastructure retry case. ExcludeConsoleLog disables Helix console-log scanning.

Error Details

 "C:\h\w\AFD40948\p\corerun.exe" -p "System.Reflection.Metadata.MetadataUpdater.IsSupported=false" -p "System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization=true"  ThreadStateDestroyed.dll
Subprocess timed out after 00:01:00.
Expected: 100
Actual: -1

The subprocess times out on Windows x86. The test was added in #132448; the check was disabled on Apple platforms in #134609 (#134571), but not on Windows. The PR's change is FEATURE_PORTABLE_ENTRYPOINTS-only (browser Wasm), so it is unrelated.

Error Message

{
  "ErrorMessage": ["ThreadStateDestroyed.dll", "Subprocess timed out after 00:01:00."],
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": true
}
Agentic workflow metadata (ci-failure-scan)

Workflow artifact: ci-failure-scan
Artifact kind: kbe-verification
Verified match count: 1 hit per signature line in failure.log

[!NOTE]
This issue was drafted with GitHub Copilot.

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1612477
Error message validated: [ThreadStateDestroyed.dll Subprocess timed out after 00:01:00.]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 9/25/2026 9:24:07 PM UTC

Report
Build Repository Test Pull Request
1612477 dotnet/runtime baseservices/threading/ThreadStateDestroyed/ThreadStateDestroyed/ThreadStateDestroyed.cmd dotnet/runtime#134606
Summary
24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 1 1
Dominant language
C#
Stars
18.3k
Forks
5.6k
Avg merge
2d 18h
Merged PRs (30d)
617

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/runtime

All issues in dotnet/runtime

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.