I have a .NET application that constantly is spending more than 40% of its time on garbage collection.
And sometimes when it gets more than 60% the application crashes. For sure that it is a sign of memory leak.
To proove it I would like to turn on the .NET Trending/Leak analysis Memory Snapshot, but firstly I would like to know how much that feature would impact process behavior/memory.
Answer by James P. ·
I would suggest doing this in Non-prod first, but if it is only occurring on production, I would suggest doing it on a specific agent. This will increase overhead, but shouldn't impact process behavior or memory significantly. If the application is crashing with an OOM exception you can also set up so that it will grab a memory dump at time, and then run a memory anyalist