C# - memory leak after calling another form

Question

0.00/5 (No votes)

See more:

Is This Problem Called Memory Leak? My Application include 5 Different Form. I Showing One of Them by Using this Code :

Form2 frm2 = new Form2();
frm2.ShowDlialog();
Form2 Includes : Buttons, TextBox, Lables, Listbox to Add Items Into the ListBox.

When frm2 Appears, It Get 1MB Memory (Based on Task Manager). After Closing Form2, The Memory Still High And it Does not Decrease. If I Call frm2.ShowDlialog() For Multiple Time, Application Memory Increased Every Time.

What I have tried:

I Searched in Google and tried :

Number 1 :

Form2 frm2 = new Form2();
frm2.ShowDlialog();
frm2.Dispose();

Number 2 : (in Form2_FormClosing)

GC.Collect();

Number 3 :
I saw articles that talking about this :

Quote:
The first place to look for leaks is in event-handling rather than missing Dispose() calls. Say your container (the parent form) loads a child form and adds a handler for an event of that child form (ChildForm.CloseMe).

If the child form is intended to be cleared from memory then this event handler must be removed before it is a candidate for garbage collection.

Note : I'm using ADO.NET in Form2_Load events. (Software Based on CRUD)

Can anyone help me?

Posted 12-Jul-22 11:25am

Member 15704684

Updated 12-Jul-22 12:58pm

v2

Add a Solution

Comments

PIEBALDconsult 12-Jul-22 20:52pm

And don't forget frm2 = null

Member 15704684 13-Jul-22 3:58am

Not works.

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)

Dave Kreskowiak · Answer 1 · 2022-07-12T12:58:00

Task Manager is lying to you.

You're seeing the memory that's RESERVED for your application, not how much it's actually using. When you dispose objects or free up any memory used, that memory goes back into the .NET heap it's maintaining for your app. It does NOT get returned back to Windows, which is what Task Manager is showing you.

If Windows needs memory returned to it, the .NET CLR will happily return whatever it can and grab new blocks of memory from Windows when needed.

If you want to see how much memory your app is really using, open up PerfMon and look at setting up appropriate memory counters for whatever you need to see.