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

AccessViolationException when profiling ASP .NET application

I am trying to profile an ASP .NET application that functions perfectly when run by itself, but when being profiled, it encounters a System.AccessViolationException "Attempted to read or write protected memory. This is often an indication that other memory is corrupt."

Specifically, this application uses the .NET duck typing library which dynamically generates code. As soon as it tries to execute the generated code, the error happens.

Any ideas?
deftflux
0

Comments

2 comments

Sort by
  • wizard_01
    I have received similar error while debugging application with child processes.
    wizard_01
    0
  • Andrew H
    I haven't seen this when trying out the duck typing library myself. Generated code shouldn't cause a problem with the profiler.

    It's possible that the profiler doesn't have enough memory to use in the process being profiled: this is currently the only way we know of that will cause this error, and only really applies to 32-bit systems. You can check for this in task manager: in general if the process is starting to use more than 1Gb of RAM or so it becomes possible for the profiler to be unable to find the memory it needs to continue.

    You can reduce the memory consumption of the process being profiled by reducing the detail level when starting it: method-level only and only methods with source both require fewer resources than line-level timing. You should also make sure that the 'simplify complex stack traces' and 'ignore extremely trivial functions' options are on: these options both try to discard results that are unlikely to be interesting yet require a disproportionate amount of storage to process.

    If this issue doesn't appear to be memory-related, would it be possible to get hold of a small piece of code that demonstrates the issue?
    Andrew H
    0

Add comment

Please sign in to leave a comment.