A corrupted linked list caused .NET createdump to consume 100% CPU forever
A corrupted linked list in the .NET createdump tool caused it to enter an infinite loop, resulting in 100% CPU usage. This issue was traced back to a missing safety assumption regarding the link_map structure during crash handling. An upstream fix has been implemented to prevent such infinite loops in the future.
- ▪The createdump tool is responsible for generating crash dumps in .NET applications on Linux.
- ▪A cyclic link_map structure led to an unbounded loop, preventing the generation of crash dumps.
- ▪The upstream fix introduces a traversal bound to ensure deterministic termination and protect against cyclic structures.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Hacker News (Newest) |
| Canonical URL | https://ruwanpurage.substack.com/p/a-corrupted-linked-list-caused-net |
| Publication time | Fri, 29 May 2026 04:46:58 +0000 |
| Retrieval time | 2026-05-29T04:59:41.898Z |
| Last seen | 2026-05-29T04:59:41.898Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | ydVFUcMIFjwi |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
A corrupted linked list caused .NET createdump to consume 100% CPU foreverI triggered a 100% CPU infinite loop in .NET createdump — and it got fixed upstreamRuwanpurage Pawan RanasingheMay 29, 2026ShareA few days ago, I was debugging a Linux process that behaved unexpectedly during crash handling.Thanks for reading Ruwanpurage's Substack! Subscribe for free to receive new posts and support my work.SubscribeInstead of producing a crash dump, the process entered a state where CPU usage remained pinned at 100%, and the dump generation never completed.That investigation led into the internals of the .NET runtime’s Linux crash tool: createdump.The result was a reproducible infinite traversal condition in ELF loader enumeration logic, later confirmed and fixed in the upstream dotnet/runtime…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Hacker News (Newest).
Discussion
0 commentsMore from Hacker News (Newest)
