The previous post found a leak whose root was a static cache, which is the case everybody recognises.
Badges
Badges come from GitHub once the author claims this feed.
Recent posts
every link opens the author’s post-
Finding a leak rooted by an event handler or a timer with an AI agent
-
Finding a memory leak in a .NET dump with an AI agent
A leak investigation has three questions, in this order: what is on the heap, who keeps it alive, and is it actually growing.
-
Diagnosing thread pool starvation from a .NET dump with an AI agent
Thread pool starvation does not hang the application, it makes it slow, and it makes it slow in a way that no profiler flags: the CPU is idle, no query is slow, and every individual operation looks fine.
-
Finding an async deadlock caused by a SynchronizationContext with an AI agent
The previous post found a deadlock by asking which thread owned which monitor.
-
Finding a deadlock in a .NET dump with an AI agent
A hang is the easiest problem to diagnose from a dump and the hardest to diagnose any other way.
-
Analyzing a .NET crash dump with an AI agent
A container restarted during the night, and this is everything the log has: Unhandled exception.
-
Speed up CI builds with Meziantou.DeltaBuild
In a monorepo, every commit or pull request can trigger a full rebuild and test of all projects even when only one small piece changed.
-
Sync vs Async File I/O in .NET: Raw Throughput, Scalability, and Buffer Size
This is a bonus post to the series about async/await in C#.
-
Migrating to runtime async
This is the last post of the series proper, with one bonus post to follow.
-
Runtime async benchmarks: .NET 10 vs .NET 11
The previous post showed what runtime async does to the generated IL.
-
.NET 11 runtime async: the runtime takes over await
Everything in this series so far has rested on one fact: async is a compiler rewrite.