C#

Every issue on C#

1. clrstack Shows the Waiter and syncblk Names the Lock Holder11 Oct 2026

   In a dotnet-dump of a contested lock, clrstack -all marked no thread as the owner. syncblk named it, and a suspended await appeared only in dumpasync.

2. A Container Given 1.2 CPUs Tells the Runtime It Has 24 Oct 2026

   Environment.ProcessorCount is the CPU quota rounded up, never below 1. The thread pool minimum follows it, and Server GC switches itself off at 1.

3. The Box You Pay For Is the One That Escapes27 Sept 2026

   Assigning a struct to an interface allocated 0 bytes. Passing it across a call boundary allocated 24. A constrained generic allocated none, until its body asked for an object.

4. The Middleware That Looked Expensive Was Not the One Spending the Bytes20 Sept 2026

   Removing UseRouting dropped per-request allocation by 2.29 KB in isolation — separated from authorization's share, routing itself costs about 24 bytes.

5. dotnet-counters Shows the Queue's Delta, Not Its Depth13 Sept 2026

   A thread pool queue held at two thousand work items read 1986 through one provider and -13 through the other, in the same second, in the same process.

6. Server GC, Workstation GC, and the Numbers Between Them30 Aug 2026

   Server GC finished 2.7 times faster and collected 17 times less often — and made the slowest request in the run 5 to 13 times slower. Both numbers are real.

7. Where Thread Pool Starvation Actually Comes From23 Aug 2026

   Blocking on a task is the case the thread pool compensates for. Blocking on a sleep or an event is the case it cannot see, and it finished 2.5 times slower.

8. The State Machine Your async Method Compiles Into16 Aug 2026

   An async method that never suspends allocates nothing. The same method, suspended once, allocates 160 bytes. The cost is not the keyword — it is the suspension.

Archive at csharpmind.com ↗