Memory Profiling Crash

• 
  Hello,
  
  What is the exception generated by the 'crash'? We may have a patch available to fix the problem.

  Brian Donahue March 12, 2008 12:09

  - 0 +
• 
  There is no exception, my application crashes.
  

  Brian Donahue wrote:

  Hello,
  
  What is the exception generated by the 'crash'? We may have a patch available to fix the problem.

  billb March 13, 2008 20:21

  - 0 +
• 
  Hvae you checked your application event logs? The exception would be logged with a source of .NET runtime and may say something about an 'AccessViolationException' or an 'InvalidProgramException'. These are the two types of exceptions for which patches to ANTS Profiler are available.

  Brian Donahue March 14, 2008 05:45

  - 0 +
• 
  There is nothing in the event log. I can simply start my application via memory profiler and shut down my app and it still claims that the app was shutdown abnormally and gathers no information.
  
  Again, I'm having no problems w/ performance profiling.

  billb March 23, 2008 13:34

  - 0 +
• 
  Actually, I may have a clue. The Take Snapshot will cause my application to crash in the memory profiler AFTER my application has created and torn down its own appdomain. If I don't create an app domain it seems to work all right. Do you have a fix for this?

  billb March 23, 2008 13:41

  - 0 +
• 
  Hi Bill,
  
  You may be onto something there. An AppDomain.Unload may cause .NET 2.0's so-called critical finalizer to kill the pipe connection between your application and ANTS Profiler. There is no way for us to prevent this from happing if this is the problem unless we can stop the finalizer thread from closing the named pipe.
  
  There is a knowledge base page about this -- although it specifically relates to performance profiling, it may also be relevant to you.

  Brian Donahue March 23, 2008 14:30

  - 0 +

Add comment

Please sign in to leave a comment.