How can we help you today? How can we help you today?

Unhandled .NET exception in memory profiler

The .NET memory profiler version 8.2 crashed while profiling with an unhandled .NET exception (but the profiled process did not crash).

Now, trying to start the profiler against the same process id reports "ANTS Memory Profiler couldn't attach to the process you selected, because another profiler is already attached to this process".

How can I clear that "flag"?
ct
0

Comments

3 comments

Sort by
  • Jessica R
    Hello,

    Thanks for your post!

    ANTS needs to set the COR_PROFILER and COR_ENABLE_PROFILING environment variables to profile your application. To clear these leftover variables from the session that ended badly, could you kindly open your registry (regedit) and search for any COR_ENABLE_PROFILING=1 and COR_PROFILER={a GUID} key pairs? Please delete them, restart your application, and you should be able to profile again. Please let us know should any issues persist!

    Thanks,
    Jessica R
    0
  • ct
    Thanks - I have not tried it, but I will the next time the app fails.
    ct
    0
  • Jessica R
    No worries, please let us know if any issues persist!
    Jessica R
    0

Add comment

Please sign in to leave a comment.