Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Basically, I have an object that I think should be garbage-collected but it’s not.
I am pretty certain all references to it are gone from what I can see in the code but for some reason, it is not getting destroyed.
Is there some way to find out what’s holding my object hostage?
There doesn’t seem to be a way to do that in Visual Studio 2005.
WinDbg perhaps?
Yes, you can use WinDbg + SOS to trace your managed heap. This link should get you started.
Note – you don’t have to use VADump (steps 1 to 3) to get a dump file, the Visual Studio debugger has this feature built in for an attached process.