Re: Garbage Collection Issues in long-standing services


"Larry Herbinaux" <LarryHerbinaux@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:3A7DB2B3-EF07-4C79-8ECF-4A0B0073D7A2@xxxxxxxxxxxxxxxx
Thanks, I will definitely try this out. In comparison with the CLR Profiler,
do you think it is easier to isolate the issues? 
....

I haven't used CLR profiler, but .NET memory profiler does a great job. You can create snapshots of all objects, compare two snapshots, show undisposed but also unreferenced (great for finding missing calls to Dispose()), live objects, their allocation stack and who referenced it. It has real time info (as program run) where you can trace number of allocated objects and you can quickly identify classes that continuosly grow in number of instances.

Regards,
Goran 

.

Loading