Profiler getting hanged when run for more than a day

Use this forum for questions on how to use .NET Memory Profiler and how to analyse memory usage.
Post Reply
ram
Posts: 2
Joined: Thu Aug 09, 2007 1:38 pm

Profiler getting hanged when run for more than a day

Post by ram » Thu Aug 09, 2007 1:48 pm

Hi,

I am trying to profile a .NET service which we are suspecting that if it were run for a long period more than 5 to 10 days with out stopping, there is some memory leak happening. But when I am trying to run the memory profiler along with it, I am not able to take a snapshot from second day it self since it is hanging for ever and once it is stopped and restarted, the application works fine and no memory leak can be reproduced.

Could an y one suggest me on how to overcome this problem.

Regards,
Ram

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

Post by Andreas Suurkuusk » Fri Aug 10, 2007 4:14 pm

The profiler should be able to profile an application for a long time. In order to help you with this problem, it would be good if you could provide us with some more information.

Is it only the profiler that hangs, or does the profiled application stop as well? Did you start the application from the profiler, or did you attach the profiler? Do you know roughly how much memory is used when you collect the snapshot? Is there a chance that the problem is caused by an out of memory condition (the profiler does add quite a lot of overhead)?

Is the unmanaged resources tracker enabled?
Best regards,

Andreas Suurkuusk
SciTech Software AB

ram
Posts: 2
Joined: Thu Aug 09, 2007 1:38 pm

Post by ram » Mon Aug 13, 2007 9:28 am

Hi Andreas,

Thanks for the reply. It is the profiler only that hangs when I click Collect Heap Snap Shot button. It shows a box Stopping Profiler please wait ... with a disabled Cancel button over it forever. My applications seem working fine. I waited for at leasat 2 hours to check if what happens or to see if my application stops along with it. But no change, I have to end profiler through Task Manager.

I started the application from the profiler. My application (Windows Service) occupies around 40 MB when run alone and is taking around 80 MB when run along with profiler. Under normal situation there is not much differance in memory while taking heap snap shot.

There is no chance of out of memory condition here. I could not find unmanaged resource traker option, I left everything with defaults. My application is pure c# windows service application in which we havent used any IDisposable classes which wrap unmanaged resources like file handles, database connections or bitmaps etc.

Please reply me with further suggestion or any other information I need to provide for better understanding.

Regards,
Ram.

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

Post by Andreas Suurkuusk » Tue Aug 14, 2007 6:45 pm

If you could provide us with log files from the profiler we would get some information about what causes your problem. Unfortunately the log files are likely to become very large if you run for more than one day (especially if a lot of instance allocations occur).

Anyway, the log files are created by supplying the /log command line parameter to the profiler executable. E.g.

Code: Select all

"C:\Program files\SciTech\NetMemProfiler\NetMemProfiler.exe" /log
This will create three log-files: ProfilerLog.txt, ProfilerClientLog.txt and AssertLog.txt. The files are created in the c:\Documents and settings\<User>\Application data\SciTech\MemProfiler3 folder. If you can zip the log-files, and they are not too big (< 10-20 MB), you can e-mail them to support@scitech.se. If they're too big, contact us at support@scitech.se and we'll provide you with information on how to upload the files to our ftp.
Best regards,

Andreas Suurkuusk
SciTech Software AB

Post Reply

Who is online

Users browsing this forum: No registered users and 27 guests