Finding objects in the finalizer queue

[mspost]

My app has a slow memory leak, and the problem is that there are lots and lots of System.Threading.ReaderWriteLock objects on the finalizer queue. I do NOT create any of these objects directly, so I would like to figure out the chain of objects creating them leading back to my objects (or perhaps a third party control).

ANTS is reporting that they are directly on the finalizer queue, but garbage colleciton is never cleaning them up.

Is there a way (I'm relatively new to ANTS) in memory profiling to indicate in advance "track the creation path of all System.Threading.ReaderWriterLock objects". I didn't see a way to do this. Is there another approach to the problem?

[Brian Donahue]

ANTS Memory Profiler is only really effective at showing the chain of references for an object and when objects are disconnected and sitting in the Finalizer, it can't really help.

But for my two cents it could be the way some using blocks are implemented.

http://stackoverflow.com/questions/278902/using-statement-vs-try-finally
_________________
Brian Donahue
Technical Support
Red Gate Software Ltd.
44 (0)870 160 0037 ext 8521
US and CAN 1-866-RED GATE ext 8521