Unhandled .NET exception in memory profiler

Memory profiling for .NET developers

Moderator: dom.smith

Unhandled .NET exception in memory profiler

Postby ct » Tue Aug 12, 2014 11:39 am

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
 
Posts: 3
Joined: Tue Aug 12, 2014 11:36 am

Postby jessica.ramos » Wed Aug 13, 2014 4:26 pm

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 Ramos
Technical Support
Red Gate Software Ltd.
jessica.ramos
 
Posts: 235
Joined: Mon Apr 23, 2012 1:13 pm

Postby ct » Fri Aug 15, 2014 12:24 pm

Thanks - I have not tried it, but I will the next time the app fails.
ct
 
Posts: 3
Joined: Tue Aug 12, 2014 11:36 am

Postby jessica.ramos » Fri Aug 15, 2014 4:20 pm

No worries, please let us know if any issues persist!
Jessica Ramos
Technical Support
Red Gate Software Ltd.
jessica.ramos
 
Posts: 235
Joined: Mon Apr 23, 2012 1:13 pm


Return to ANTS Memory Profiler 8

Who is online

Users browsing this forum: No registered users and 0 guests