I have used the ANTS Memory Profiler successfully on a few different applications, but we are currently having an issue with one particular WPF client running on .NET 3.5 SP1. Anytime I try to take a snapshot, the application crashes (our application crashes, not the memory profiler itself) with the standard Windows error "this application has stopped working, looking for solution blah blah blah".
It seems to me that the profiler should not affect the behavior of the process it is attached to, so I don't think I could be doing anything wrong. Is this a known bug? Is there anything I can do to get around it?
We have tried versions 5 and 6 of the memory profiler, but both have the same issue.
The SciTech .NET memory profiler works fine on our application, but I really prefer to use ANTS when it works so any advice would be greatly appreciated.