Who calls gc.collect() in C#? Is it a CLR?

Question

0.00/5 (No votes)

See more:

Who calls GC.Collect() in C#? is it a CLR?

What I have tried:

I have tried to find the working of GC.Collect() but I didnt find any good article. Please help to understand the caller of the GC.Collect()

Posted 22-Mar-17 18:32pm

Chaitali Patkar

Updated 22-Mar-17 20:31pm

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)

Suvendu Shekhar Giri · Answer 1 · 2017-03-22T18:55:00

Solution 1

Quote:
Who calls GC.Collect() in C#? is it a CLR?

It's you (your code) who calls GC.Collect(), I belive.

GC.Collect Method (System)[^]
When to call GC.Collect() – Rico Mariani's Performance Tidbits[^]

Posted 22-Mar-17 18:55pm

Suvendu Shekhar Giri

OriginalGriff · Answer 2 · 2017-03-22T20:31:00

In effect, you do: it's just done behind the scenes.
When you create a new instance of a class, the space needs to be allocated on the heap. The allocation system looks for a suitable "chunk" of memory to use, and if it doesn't find one, it calls the garbage collector to try and free some up.
If you think about it, it's the only sensible time to do it - you need the memory, so that's when the time must be taken to find it!

That's why it's very important to use Dispose (or a using block) to ensure that precious resources are released: if you don't Dispose of a file stream when you are finished with it, then the file remains open until the app closes or the GC is called by you running out of memory - this is very often why people get "file in use" errors and can't work out what is using it!