When I start profiling my console app. it immediately gives me the CLR Debugging Services error box - "Application has generated an exception that could not be handled. Process id=2608." Click Cancel to debug
and I find its a nullreference exception. Then everything closes.
My code does reference the redist DLL, as I have some calls to
take snapshots, in code.
.NET SDK 1.0, 1.1 and 2.0 installed.
Works fine with MemProfiler v2
Can't see any logs in the program files dir.
Obviously there are a lot of settings - I'd rather not list them all...
If I can help by sending something, please let me know. If there's some setting I can set to avoid this, that would be great!
The instruction at "0x0371ca11" referenced memory at "0x77e68b98". The memory could not be "written".
It would be good if you could provide us with some more help on this problem. Do you have any additional information about the NullReferenceException (maybe a stack trace)? Is it possible for you to send us an application that reproduces this problem? Or can you send us log-files from the profiler when this problem occurs?
To create the log files you must supply the "/log" command line argument to the profiler executable (NetMemProfiler.exe). This will create three log-files in the program directory: ProfilerLog.txt, ProfilerClientLog.txt and AssertLog.txt (AssertLog.txt will probably be empty). After you have created the log-files, you can send them to firstname.lastname@example.org (preferably zipped).
Regarding the problem with the profiler crash. As long as the user doesn't perform any action, the profiler should not execute any code (except the framework itself). There are no timers and no idle processing, so it's very confusing how the profiler can just crash.
We will look into this problem as well, but we don't have much to go on without some additional information. Does this happen each time you start the profiler? Are you able to reproduce it on another computer?
SciTech Software AB
I enabled logging, and started the profiler, I left it in the background (without starting to profile an app.) and it crashed after a few seconds with only one log file written.
ProfilerLogger: 09/04/2006 19:49:46  INFO: Updating snapshot combos
ProfilerLogger: 09/04/2006 19:49:46  INFO: Snapshot combos updated
ProfilerLogger: 09/04/2006 19:49:46  INFO: RetrieveSnapShotData, showItem=Empty, compareItem=Empty
Not too helpful I dont suppose.
Then I tried profiling my app., and I debugged it, and got the following stack trace:
I will send the logs to the email you spec'd.
With regards to the app., it doesn't matter what it does - it crashes even with an exe that does just this
static void Main(string args)
Why does it hate me?
We're currently finishing some major restructuring of the profiler, so the behaviour you're seeing might have changed in the next release. As soon as we have a new version I will contact you and provide you with the new version. If you then still experience the same problem, we will have to investigate it further.
SciTech Software AB
Users browsing this forum: Bing [Bot] and 22 guests