Comments
8 comments
-
Hi Cory,
Would it be possible for you to try profiling in Fast Mode rather than Detailed Mode, and see if you still get the problem?
Also, are you getting these errors in more than one separate application (this could be slightly hard to determine if they're sharing common assemblies)? If you could get a sample that reproduces the problem that you're able to send us, that would be fantastic, but I do realise this could be tricky.
Many thanks,
Robert -
Another thought is if you could send us just a debug build and the pdb file without the source code that should give us enough information to locate the reason for the Invalid program exception.
Also out of interest..
in .net 1.0 (now not supported), 1.1, 2.0 or 3.0?
running in 32bit or 64bit mode?
which language are you using?
Any help you can give us would be great. -
I can profile in Fast mode fine and then re-run a compile with Detail mode without touching the application and it will fail. I usually get the "Failed to load module from assembly MyAssembly, Version=0.5.0.6, Culture=neutral, PublicKeyToken=null. Error was:
Attempted to read or write protected memory. This is often an indication that other memory is corrupt.", but sometimes the Invalid program.
I will see if I can send a build version of the app. The problem is that it is a very large app with a variety of dependencies. -
Another thought is if you create a directory in the location you installed ANTS Profiler called 'Logs' and send us a copy of the corelog.txt that gets created we may be able to get more idea about where the problem is. There is obviously some issue that we are creating when we instrument the code for detailed mode.
-
Richard,
How would you like me to get you the log files from the Logs directory I created in the ANTS Profiler 3 folder. I just received the error again.
<ExceptionType>System.AccessViolationException, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
<Message>Attempted to read or write protected memory. This is often an indication that other memory is corrupt.</Message>
<Source>Regis.Framework.WinForms</Source>
Cory -
-
I'll send them.
Cory -
I think we've got it. We managed to get a test case for the Access Violation Exception and hopefully we've nailed it for the release.
Thought you should know
Add comment
Please sign in to leave a comment.
The Message of the InvalidProgramExceptions states "Common Language Runtime detected an invalid program."
The Message of the AccessViolationException "Attempted to read or write protected memory. This is often an indication that other memory is corrupt."
These errors only occur when I am running under the profiler. They are occuring in my application that uses WCF and WF. I'm not sure if these exceptions are related to this or not, but I have only been working with these types of applications. I'm not sure that I would be able to send you a copy of the application since it is for a client of ours. It seems sometimes if I switch from Debug or Release mode or vice versa it works. I have to keep trying to switch the mode until I can get a compile that works. This is very frustrating as this can take quite a while to get working.
Is there anything I can do to get around this. Any help would be greatly appreciated. Please let me know if you have any questions.
Thanks,
Cory