Diagnosing .NET memory dumps in Visual Studio 2022
Vložit
- čas přidán 7. 11. 2021
- When unexpected errors occur in your managed application you are often left with little evidence of the issue; capturing and analyzing memory dumps may be your last best option. Thankfully, Visual Studio is a great tool for analyzing your apps memory dumps! In this video we show you how easy it is to get important insights from a memory dump.
aka.ms/VS2022LaunchLearnTV
visualstudio.microsoft.com/la...
Intro
Capturing a memory dump
Debugging unhandled exceptions
Debugging a memory leak
Debugging a deadlock
#vs2022 #dumpdebug - Věda a technologie
Your presentation is concise and very helpful at the same time. You have a talent in presenting. Thank you!
Excellent video. Thank you!
Excellent video. Thank you!!!!!
This is extremely helpful. Excellent tutorial.
Great tutorial!
Great work!
Now we know who behind the scene create a better world!
haha Microsoft and better world. Choose one.
If I understand correctly, this dotnet-gcdump is for .NET Core 3.1 or higher. Is there anything similar for .NET Framework 4.5? I got an old system that I wanted to check a memory leak that uses .NET Framework 4.5.
I wrote a comment before, but weirdly, it doesn't show up. I am trying to debug the veracrypt.sys driver, and my system freezes. At least I can do a right-ctrl + scroll lock (x2) and get a .dmp file, but I'm not sure which type of .dmp file I should be generating: small memory dump, kernel, automatic? And visual studio 2019 sucks for working with .dmp files because it doesn't ask me to load the symbols file for my program. dotnet-gcdump seems to only work with .dll or .exe and I want to see if I can fix this driver to keep it from freezing my system. I see that Qcamain is in the bucket id, but when I disable my wireless network driver which has that name, I still get the freeze, although a bit less frequently. When I do a dump, I still see that bucket id.
HI ! I've tried and it's ok when I run visual studio in the same pc, but in another pc symbols can't be loaded and I can't decompile.
How can I do ?
Newbie question sir,Does asynchronous threads resolves the deadlock issue? Thanks in advance.
But you didn't mention in the third deadlock scenario whether you are running the app on VS or over a dump file. Can you clarify please?
Is WinDbg no longer recommended in analyzing memory dumps?
Visual Studio became so smart, nobody can come close
Bookmarked
You didn't link the tools you use in the description like your video said.... disappointing.