We have purchased a license of the profiler for a while and we quite enjoyed it. Recently I was using its VS2010-integrated "Debug with Memory Profiler" capability to investigate a memory leak. Our application is a WinForm application using 3.5 runtime. Profiler version is the latest 184.108.40.206
What happened is the profiler ran successfully for a couple of times, I can pause the execution, step-in, step-out, take a snapshot etc, all good. But after I found the leaking point and fixed the issue, and when I tried debug with profiler again to verify my fix, I have an error saying "An unhandled exceotion of type System.Runtime.Serialization.SerializationExeception occurred in xxxx.nmphost.exe". Sometimes it is another exception related to reflection. A message box poped up asking if I want to "Break" or "Continue". If I break, there is no source code available at the breaking point. If I continue, the application just terminated. I cannot ignore the exception since the "Ignore" button is disabled.
I tried rebuild, problem was not fixed.
I tried start profiler inside vs2010 without debugging, I didnt see the exception message box, however the application just terminated unexpectedly.
I tried launch or debug my application without profiler, everything went well, no exception at all.
I also tried to build a release version of my application and profile it with the standalone profiler, no issue.
I just cannot debug with profiler after my change.
Is there any way to investigate the issue?
You can create log-files by using the command line below. This will create a set of log-files in the c:\MemProfilerLogs directory.
"C:\Program Files\SciTech\NetMemProfiler4\NetMemProfiler.exe" /log:c:\MemProfilerLogs
Can you send the log-files to firstname.lastname@example.org so that we can investigate this further?
SciTech Software AB
Users browsing this forum: No registered users and 18 guests