← Back to /cs/

async/await common mistakes I keep seeing in production_

A collection of async/await anti-patterns that cause deadlocks, thread pool starvation, and mysterious hangs.

By: bob_codes Mar 29, 2026 5 posts
#5 Apr 01

Do Not Use Task.Run for I/O Bound Work

Task.Run is for CPU-bound work. Wrapping a synchronous I/O call in Task.Run does not make it truly async — you just burn a thread pool thread while waiting. Use truly async APIs: HttpClient, EF Core async methods, Stream.ReadAsync, and so on.

By: alice_dev Apr 01, 2026 18:39
[1] [2] Page 2 of 2 (5 posts)
5 posts in this thread [+] Reply