Debugging Memory Leaks in .NET with Adam Furmanek
Memory Leaks in .NET? How is that possible? While at .NET Developer Days in Warsaw, Carl and Richard talked to Adam Furmanek about modern memory leaks - the things we can do in .NET that cause more memory to be consumed over time. Adam talks through various aspects of .NET that have a risk of causing memory leaks, how to detect them and then the hard part - how to fix them.
Guests:
Adam Furmanek
Adam Furmanek has been working as a .NET developer since 2012. He currently works at Amazon with Scala, Spark and Machine Learning. Adam is always interested in digging deeper, exploring machine code and going through implementation details to better understand internals of the technologies he uses every day. He likes to play ping-pong, watch Woody Allen's movies and blog stuff at http://blog.adamfurmanek.pl
Links:
- Wyze Cam https://wyze.com/
- Finalizers https://docs.microsoft.com/dotnet/csharp/programming-guide/classes-and-structs/destructors
- WinDbg https://docs.microsoft.com/windows-hardware/drivers/debugger/debugger-download-tools
- Unsafe https://docs.microsoft.com/dotnet/csharp/language-reference/keywords/unsafe
- ArrayPool<T> https://docs.microsoft.com/dotnet/api/system.buffers.arraypool-1?view=netcore-3.0
- Span<T> https://docs.microsoft.com/en-us/dotnet/api/system.span-1?view=netcore-3.0
- Advanced .NET Debugging https://www.oreilly.com/library/view/advanced-net-debugging/9780321584090/