Röck Yoür Cöde: Everything That .NET Developer Needs to Know About Disposable Types
summary
Claim: improper disposal of reference types creates virtual memory leaks that force service reboots and stifle throughput. Evidence: a codebase shows 600 missing disposes and 90 faulty IDisposable types, requiring ~2,000 fixes and raising concurrency from 700 to ~7,000. Tools and fixes: an open source extension (Sparen) that disposes fields, plus IDisposable.Analyzers and .NET Memory Profiler to find issues. Concrete practices: use using blocks, implement IDisposable correctly, run memory profiling before release.
AI-written summary · about
chapters (6)
- 0:00Disposable types intro
- 6:58Why disposables matter in .NET
- 17:55Implementing IDisposable
- 26:57Pitfalls and advanced scenarios
- 31:45Finding disposable issues
- 39:40Memory profiling and tips
related talks
53mDebugging .NET Apps
01h 04mAdvanced .NET debugging techniques from real world investigations
47mSolving .NET performance issues
33mMemory Profiling for Mere Mortals
01h 00mDiagnosing issues in ASP.NET Core Applications
22mHunting down memory leaks with PHP Meminfo
36mMemory Why You Need to Care
20mBehind the Code: Design Choices in OpenTelemetry .NET Metrics API and SDK
