Memory Leak in windows app

Question

0.00/5 (No votes)

See more:

.NET2.0

hi,

Please do not mark this question as repost , i posted a question on memory leak , placed this in comments , no response so reposting it .

for my windows application developed in C#.NET 2.0

I tried to debug the issue using Debugdiag , it showed memory leak in below libs ,

these are the dlls where leak occurs , over i period time the leak for these dlls increases , leading to application crash, Please suggest what can be done.

I am using .NET framework 2.0 and my application is 32 bit.

mscorwks.dll is responsible for 121.05 MBytes worth of outstanding allocations. The following are the top 2 memory consuming functions:

mscorwks!EEVirtualAlloc+119: 120.69 MBytes worth of outstanding allocations.

mscorwks!DebuggerHeap::Alloc+2f: 284.07 KBytes worth of outstanding allocations. If this is unexpected, please contact the vendor of this module, Microsoft Corporation, for further assistance with this issue.

Warning WindowsCodecs.dll is responsible for 13.51 MBytes worth of outstanding allocations. The following are the top 2 memory consuming functions:

WindowsCodecs!WPF::ProcessHeapImpl::Alloc+16: 13.43 MBytes worth of outstanding allocations.

WindowsCodecs!zcalloc+1c: 86.67 KBytes worth of outstanding allocations.

Thanks,
Shreyas

Posted 11-Oct-13 9:33am

srastogi85

Add a Solution

Comments

Ron Beyer 11-Oct-13 15:40pm

Just because they are in factory DLL's doesn't mean your application isn't responsible for them. How can we help see where your code is leaking using these libraries if you don't post it?

srastogi85 11-Oct-13 15:57pm

Hi Ron,
I understand , actually its a big enterprise application with using DTOs and objects from Infragistics , sorry cant post the code as its not possible wanted to have some idea how to debug or identify the issue.
Thanks

Mike Meinz 11-Oct-13 16:02pm

If you can't post your company's proprietary application code, then create a small test program that demonstrates the issue and post that code.

1 solution

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)

Mike Meinz · Answer 1 · 2013-10-11T10:07:00

Are these COM DLLs?
If so, you have to be sure to properly release the .NET objects used with the COM object.
See How to Release COM Interop Objects so the Called Program Can Exit[^]

Also, see these articles:
Unmanaged memory leak in mscorwks help analyze[^]

FIX: A memory leak occurs when a managed application uses a platform invoke call to call an unmanaged function in the .NET Framework 2.0[^]

FIX: You may notice that the memory load is very high when you run an application that is built on the .NET Framework 2.0[^]

... more available via Google search