Datasets in Windows Forms building memory heaps

Question

0.00/5 (No votes)

See more:

I am novice to Win Forms. My application keeps on building up memory and not releasing it back to system. I have tried disposing off all the datasets created and the forms have been closed and disposed. Somehow the Garbage Collector is not freeing up the memory.
I have used the memory profilers and find that the queries build for the datasets are still kept in the memory.
I suspect the big "aaa.xsd" files that are formed to create huge query strings - that are "User Non debugger code"......what system did generate when doing the datasets.
Is their any way to clear off the query strings , that is what I suspect is holding up the memory.
I hope I have put up the question in a detailed fashion. Please feel free to ask more questions if need be.
Thanks for reading this and replying.

Posted 6-Jul-11 18:14pm

shalini.nikharey

Add a Solution

2 solutions

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)

Dave Kreskowiak · Answer 1 · 2011-07-06T19:09:00

If you're looking in TaskManager, that's your first mistake.

Your code runs in a type of virtual machine, managed by the .NET CLR (Common Language Runtime). The CLR maintains a "managed" heap of memory for your application to use. That heap is allocated out of memory handed over by Windows.

When your code runs, it starts allocating its object out of the managed pool of memory. If the managed pool runs low on free memory, the CLR asks Windows for more memory and adds it to the managed heap.

Task Manage is showing you the memory reserved for your application, not what it is actually using!

When your application frees objects, the memory goes back into the managed heap, not back to Windows.

The .NET CLR does a very good job of managing memory. If Windows needs memory back form the CLR, the CLR is more than happy to return whatever memory it can, which is usually a pretty good sized chunk.

If you want to see how much memory your code is really using, use PerfMon and the .NET Memory counters.

shalini.nikharey · Answer 2 · 2011-07-14T15:27:00

I have used a memory profiler (Redgate ANTS) to profile the application.
The CLR is obviously not doing the right thing not releasing enough memory into the OS.
Is it a flaw with Win Forms that it acquires lots of memory to run?
Web Apps are better in case of memory utilisation ??

I hsve tried practically every optimisation technique and the memory still keeps piling up.

Datasets in Windows Forms building memory heaps

2 solutions

Solution 1

Solution 2

Add your solution here

Preview 0