Correcting Common Mistakes When Using Async/Await in .NET
summary
Explains how the .NET compiler rewrites async methods into compiler-generated state machines and why that causes extra allocations and larger binaries, shows common mistakes like async void pitfalls and forgotten awaits that let exceptions escape, and demonstrates concrete fixes that halve allocations and cut tail latency, with before-and-after timings and binary-size measurements. Includes small code changes and compiler flags that actually reduce crashes and memory overhead.
AI-written summary · about
related talks
01h 01mBack to Basics: Efficient Async and Await
01h 02mBack to Basics: Efficient Async and Await
01h 15mBest Practices for Using async and await
46mAsynchronous Processing and Multithreading Are Always Fun
22mHave You Heard the Joke About Async Debugging? I Promise It Is Good
27mManeuvering Errors Within the Bowels of JavaScript
30mHow to Test Asynchronous Code
02h 44mMeasure, don’t guess: benchmarking stories from the trenches