Why does taking a snapshot kill the process being profiled?
The process was built using VS 2019 and Postsharp 6.6.10. It targets .NET 4.0 running under Win 10 Enterprise.
I click on take a snapshot and get a pop-up telling me that the process has stopped working. I tried leaving it for 10 minutes, but nothing changed.
Any idea why I cannot profile what is a simple process? I took out the GUI and had the whole thing running under a simple command line. The process is single threaded with no async operations. I'm trying to track a leak in a library - the process is as simple a wrapper as I can put around the library to call into its functionality.
Am I being hasty in killing the process?
For the record. Using the default settings for a profiling session.
It seems to be windows killing the process about 20 seconds into the snapshot. I assume that the process freezes the running thread until the GUI is answered. If anyone knows a way to stop windows killing the process so quickly - that would be a help.
0 · Share on Twitter