Memory leak .NET 2.0

Question

2.22/5 (3 votes)

See more:

.NET2.0

Hi,

Is it possible to free all unmanaged resources in the middle of the windows application run,
I'm running a C#.NET 2.0 application as it is causing an issue .

Thanks,
Shreyas

Posted 24-Sep-13 11:28am

srastogi85

Updated 24-Sep-13 11:33am

Eduard Keilholz

v2

Add a Solution

Comments

Sergey Alexandrovich Kryukov 24-Sep-13 17:33pm

Why on Earth?!
—SA

Matt T Heffron 24-Sep-13 17:38pm

+4 for the question to offset the 1.
The question itself is reasonable.
The proposed/asked approach to the symptom is not reasonable.

4 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 · 2013-09-24T12:18:00

If you're asking how to clean up thing you've done wrong in the middle of the application, then NO, you can't. Well, not without quitting your application and launching it again.

The reason being is that you're leaking resources because you orphaned them by letting the pointer to them drop out of scope without properly disposing them in the first place.

The REAL solution to this is to identify the leak, why it's occurring (HINT: YOU didn't do something correctly) and modifying the code to properly clean up after itself.

Sergey Alexandrovich Kryukov · Answer 2 · 2013-09-24T11:33:00

Solution 2

Only if you design the use of your unmanaged resources that way. But I think it would be difficult and totally pointless. The reasonable practice is to free the resources as soon as you don't need them. All .NET FCL classes are using unmanaged resources are designed this way.

—SA

Posted 24-Sep-13 11:33am

Sergey Alexandrovich Kryukov

Eduard Keilholz · Answer 3 · 2013-09-24T11:32:00

Solution 1

Yes this is possible, I would however consider when and how you release those resources. To correctly free the resources one good way is to have the IDisposable interface implemented.

See this[^] page for an excellent example.

Good luck!
Eduard

Posted 24-Sep-13 11:32am

Eduard Keilholz

Comments

Sergey Alexandrovich Kryukov 24-Sep-13 17:35pm

I don't really think this is what OP is asking about, which hardly can be reasonable. Please see my answer.
—SA

Dave Kreskowiak · Answer 4 · 2013-09-24T12:19:00

If you're asking how to clean up thing you've done wrong in the middle of the application, then NO, you can't. Well, not without quitting your application and launching it again.

The reason being is that you're leaking resources because you orphaned them by letting the pointer to them drop out of scope without properly disposing them in the first place. Without the pointer, there's no way to properly free the unmanaged resource. There is no way to get that pointer back once you've lost it!

The REAL solution to this is to identify the leak, why it's occurring (HINT: YOU didn't do something correctly) and modifying the code to properly clean up after itself.

Memory leak .NET 2.0

4 solutions

Solution 3

Solution 2

Solution 1

Solution 4

Add your solution here

Preview 0