windows service only leaks Memory when running from Profiler

Use this forum to discuss subjects that don't belong in the other forums.
Post Reply
Posts: 1
Joined: Wed Oct 24, 2007 5:50 am

windows service only leaks Memory when running from Profiler

Post by Vishalp » Wed Oct 24, 2007 5:57 am

Hi there,

I recently bought your software version enterprize 3.0.

My application run as windows service.
When I run my application it uses around 50 -75 MB memory.
But when I run with the .Net Memory Profiler Memory Keeps increasing and go up to 800 MB.

I have tested both scenario for hours.
I'm doing my application's stress testing.
Stress testing is perfectly fine whithout running from Memory Profiler.
But when I run from Memory Profiler it just keeps increasing.

I have observed with task manager and performance monitor.
Both gives similar results.

Is there any known issue with the given version?
What are the other possibilities it can have?

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

Post by Andreas Suurkuusk » Wed Oct 24, 2007 7:57 pm

One thing that can cause the memory usage of the profiler to increase, is dynamically generated types. The profiler keeps track of all loaded types in the process, and it never removes the type information, even if the type is unloaded. The reason for this is that a snapshot can contain information about any type that has ever existed in the process (e.g. it should be able to tell that 100 instances of DynamicType123 has been allocacted, even if DynamicType123 has been unloaded).

Does your service create any dynamic types? If you collect a snapshot, how much memory usage (managed and unmanaged) is presented by the profiler? Do you still see this high memory usage if you disable the unmanaged resources tracker?
Best regards,

Andreas Suurkuusk
SciTech Software AB

Post Reply

Who is online

Users browsing this forum: Majestic-12 [Bot] and 18 guests