Diagnosing issues in ASP.NET Core Applications
summary
Covers concrete failure modes in ASP.NET Core: thread starvation when code blocks or creates threads per request (demo shows running out of thread-pool threads at ~10 concurrent blocking requests causing timeouts and cascading failures), ANCM port/client-port exhaustion between IIS and backend, lost shadow‑copy deploy behavior and app_offline quirks, race conditions from shared collections and no synchronization context (Dictionary corruption, duplicate continuations), unsafe use of IHttpContextAccessor, and creating HttpClient per request. Shows fixes: use async end‑to‑end, concurrent collections or locking, singleton/reused HttpClient, app verifier/blocking detector and temporary thread‑pool tuning.
AI-written summary · about
chapters (9)
- 0:00Start
- 4:34The Asp Net Temporary Files Folder
- 5:00Shadow Copy Directories
- 8:07The Asp Net Core Module
- 15:10Dictionary Corruption
- 17:25Demo
- 43:22Blocking Detector
- 45:11App Verifier
- 45:56Demos
