Version 3 preview, crash

Use this forum for questions on how to use .NET Memory Profiler and how to analyse memory usage.
Post Reply
jim
Posts: 5
Joined: Mon May 01, 2006 6:04 pm

Version 3 preview, crash

Post by jim » Thu Aug 31, 2006 6:52 pm

Hi, I'm a version 2 customer who needs the unmanaged resources tracker in v3. I have had the following problem with both releases of the v3 preview.

The error:

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.

Some info:
My code does reference the redist DLL, as I have some calls to
take snapshots, in code.
XP SP1
.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!

Thanks
Jim

jim
Posts: 5
Joined: Mon May 01, 2006 6:04 pm

More info

Post by jim » Thu Aug 31, 2006 7:07 pm

Also, if I just open the profiler, and do *nothing* with it, dont specify an exe, just do nothing. After about a minute it crashes with

The instruction at "0x0371ca11" referenced memory at "0x77e68b98". The memory could not be "written".

Jim

Andreas Suurkuusk
Posts: 1029
Joined: Wed Mar 02, 2005 7:53 pm

Post by Andreas Suurkuusk » Fri Sep 01, 2006 3:00 pm

We are aware of some problems in the preview of .NET Memory Profiler 3.0, but we have not heard of a problem that is similar to yours.

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 support@scitech.se (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?
Best regards,

Andreas Suurkuusk
SciTech Software AB

jim
Posts: 5
Joined: Mon May 01, 2006 6:04 pm

Post by jim » Tue Sep 05, 2006 3:04 am

Thanks Andreas, thanks for the offer to help - I'm happy to give you anything I can that will help you.

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.

ProfilerClientLog.txt

ProfilerLogger: 09/04/2006 19:49:46 [1] INFO: Updating snapshot combos
ProfilerLogger: 09/04/2006 19:49:46 [1] INFO: Snapshot combos updated
ProfilerLogger: 09/04/2006 19:49:46 [1] 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:

> 7ffe0304()
ntdll.dll!77f5c534()
kernel32.dll!77e689a9()
kernel32.dll!77e68bd7()
mscorwks.dll!79297cc3()
mscorwks.dll!792991c0()
mscorwks.dll!792475db()
mscorwks.dll!793a3591()
mscorwks.dll!793a3736()
mscorwks.dll!792b0565()
mscorwks.dll!792b0651()
kernel32.dll!77e94c30()
kernel32.dll!77e735e8()
ntdll.dll!77f59037()
ProfilerCallbackLog.dll!1000d6d3()
ProfilerCallbackLog.dll!10022436()
ntdll.dll!77f8c366()
ntdll.dll!77f8c44a()
ntdll.dll!77f8c430()
ProfilerCallbackLog.dll!10038cac()
ProfilerCallbackLog.dll!1002e6ce()
ProfilerCallbackLog.dll!1002de92()
ProfilerCallbackLog.dll!10036914()
ProfilerCallbackLog.dll!1002da86()
ProfilerCallbackLog.dll!1002da7d()
ProfilerCallbackLog.dll!10036914()
ProfilerCallbackLog.dll!1002fdef()
ProfilerCallbackLog.dll!1002fde6()
ProfilerCallbackLog.dll!1005c4dd()
ProfilerCallbackLog.dll!1005c4ed()
ProfilerCallbackLog.dll!1005c2eb()
ProfilerCallbackLog.dll!1000c4bf()

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

[STAThread]
static void Main(string[] args)
{
Console.ReadLine();
}

Why does it hate me?

Thanks!
Jim

Andreas Suurkuusk
Posts: 1029
Joined: Wed Mar 02, 2005 7:53 pm

Post by Andreas Suurkuusk » Tue Sep 05, 2006 9:08 pm

You have really found a strange error :? .

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.
Best regards,

Andreas Suurkuusk
SciTech Software AB

jim
Posts: 5
Joined: Mon May 01, 2006 6:04 pm

Post by jim » Tue Sep 05, 2006 9:15 pm

Thanks - that would be great.

Jim

Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 22 guests