Memory leakage problem

Question

4.00/5 (1 vote)

See more:

Hi,

My winService (written in C#) is consuming 1.5GB (starts from few MBs and then grows) of memory due to usage of Byte arrays.

I have tried:

C#

Bytearrays=null;

but didn't work for me.

please note: I am using some third party Dlls (unmanaged code).

Please help??

Posted 8-Jun-12 0:37am

Vipin_Arora

Updated 8-Jun-12 2:03am

v4

Add a Solution

Comments

Oleksandr Kulchytskyi 8-Jun-12 7:14am

Do you call from your service any unmanaged code/resources??

Vipin_Arora 8-Jun-12 8:01am

yes, we are using third party Dlls (unmanaged code)

3 solutions

Solution 2

Along with solution 1 mentioned by Mehdi Gholam below is explanation and addition.

Try to set bytearray = null as soon as you are completing consuming it.

You have not mentioned when are you consuming bytearray and when are you setting it to Null.

In addition you also might need to Collect generation 2 objects from GC. Refer Large Object Heap Uncovered[^].

Also let us know how are you calling/passing bytearray to unmanaged code, are you passing any buffer/length. Tried to pass buffer/length.

Thanks
Rushi

Posted 8-Jun-12 3:26am

Joshi, Rushikesh

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Mehdi Gholam · Accepted Answer · 2012-06-08T00:47:00

Solution 1

As a last resort (not recommended) try :

C#

GC.Collect(2);

Posted 8-Jun-12 0:47am

Mehdi Gholam

Comments

codeBegin 8-Jun-12 6:52am

to the point +5

Mehdi Gholam 8-Jun-12 7:00am

Thanks

Joshi, Rushikesh 8-Jun-12 9:27am

+5 for giving a direction :)

Dave Kreskowiak · Accepted Answer · 2012-06-08T03:57:00

First, what's telling you that you're service is useing 1.5GB of RAM?? If you're lookin in Task Manager, it's lying to you.

In simple terms, the .NET CLR RESERVES memory for your application, called the Managed Heap. Any objects you allocate in your app, like an array are allocated out of the Managed Heap. When you free that object, the memory is returned to the Heap, NOT to Windows! Since your application used a ton of memory in the past, the .NET CLR will try to hang on to that memory so that future allocations of any objects happen quickly.

But, if Windows needs the memory back, the .NET CLR is more than happy to return any unused Manage Heap memory back to Windows.

Task Manager looks at memory usage from Windows point of view, not from the .NET CLR.

So, if you want to see how much memory you app is REALLY using, you have to use PerfMon and the .NET Memory counters or a memory profiling tool, such as these[^], or if you're using Visual Studio 2010, you can use the built in profilers.