Operation could destabilize the runtime

Code profiling for .NET developers.

Operation could destabilize the runtime

Postby cedric.petter » Thu Aug 08, 2013 6:44 am


I use Ants Profiler since some years to profile SharePoint and everything is fine.
But since version 8.2 I'm not able to profile SharePoint 2013.

Each time I "start profiling" the system will start correctly and then I have "Operation could destabilize the runtime" error in SharePoint.

Everything works fine if I don't use ANTS Profiler !

Does someone has the same problem?


Posts: 2
Joined: Thu Aug 08, 2013 6:40 am

Postby Chris.Allen » Mon Aug 12, 2013 11:34 am

This is what Microsoft say about profiling and latest sharepoints. I hope it might help:

// Uncomment the following SecurityPermission attribute only when doing Performance Profiling on a farm solution
// using the Instrumentation method, and then remove the SecurityPermission attribute when the code is ready
// for production. Because the SecurityPermission attribute bypasses the security check for callers of
// your constructor, it's not recommended for production purposes.
// [System.Security.Permissions.SecurityPermission(System.Security.Permissions.SecurityAction.Assert, UnmanagedCode = true)]
Posts: 579
Joined: Thu Mar 12, 2009 3:17 pm

But where?

Postby cedric.petter » Mon Aug 12, 2013 11:38 am

Hi Chris

Thanks for your answer.
But I don't know where I have to uncomment this code !
I don't have this in all my code !

Posts: 2
Joined: Thu Aug 08, 2013 6:40 am

Return to ANTS Performance Profiler 8

Who is online

Users browsing this forum: No registered users and 0 guests