In .NET framework who allocates memory to object in managed heap?

Question

1.24/5 (3 votes)

See more:

If I make any object for example :

Emp obj= new Emp();

So who clr , system(OS) or garbage collector will allocate memory to obj object in heap ?

1. Extract 1 :Which concludes garbage collector is responsible.
From micorsoft
link -<a href="https://msdn.microsoft.com/en-us/library/f144e03t(v=vs.110).aspx">
</a>
Extract :When the application creates the next object, the garbage collector allocates memory for it in the address space immediately following the first object. As long as address space is available, the garbage collector continues to allocate space for new objects in this manner.

2.Extract 2: Which concludes clr will be responsible for memory allocation and gc will only be called if heap is full.

link -
[^]

Can anybody really tell me if gc is really responsible for allocating memory to an object.

What I have tried:

1. Extract 1 :Which concludes garbage collector is responsible.
From micorsoft
link -<a href="https://msdn.microsoft.com/en-us/library/f144e03t(v=vs.110).aspx">
</a>
Extract :When the application creates the next object, the garbage collector allocates memory for it in the address space immediately following the first object. As long as address space is available, the garbage collector continues to allocate space for new objects in this manner.

2.Extract 2: Which concludes clr will be responsible for memory allocation and gc will only be called if heap is full.

link -
[^]

Posted 24-Apr-16 0:00am

praveen iThesisArt

Updated 24-Apr-16 0:46am

v2

Add a Solution

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)

OriginalGriff · Accepted Answer · 2016-04-24T00:09:00

Solution 1

Both: the Garbage Collector is part of the CLR and works to clean up after you and free memory. It is in control of the Heap and it's free memory lists, so it also does the allocation of memory: Automatic Memory Management[^]
The system allocates the memory to start with when your app starts (and for each thread you start as they all have independent stacks which are not controlled by the GC), and the GC is responsible for it after that.
Listen to what MSDN says, not a third party like Telerik - and if you really need to know the details, I'm sure the GC is buried somewhere deep in the Reference Source[^]

Posted 24-Apr-16 0:09am

OriginalGriff

Comments

praveen iThesisArt 24-Apr-16 6:37am

So , when i write code :
Emp obj= new Emp();
Memory for obj will be allocated by gc?

OriginalGriff 24-Apr-16 6:50am

Assuming Emp is a class and not a struct, yes.
If it's a struct, then it's a Value type not a Reference, so it will go on the stack, not the heap.

praveen iThesisArt 24-Apr-16 6:52am

So if emp is a class, memory will be allocated by GC?

OriginalGriff 24-Apr-16 6:57am

Yes.

praveen iThesisArt 24-Apr-16 9:47am

Then who will allocate de-allocate memory in stack (value type as in case of struct) ? 'coz gc doesnt work over stack . So is it clr or compiler or processor of a system will take call on this?

OriginalGriff 24-Apr-16 10:07am

OK... :laugh:
It's automatic and is handled by the compiler. It "knows" how much stack space it uses so as part of the normal "return" instruction processing it uses a frame pointer to locate the stack pointer back to where it was when it entered the method, and then takes it's return address off the stack and goes back to it.
This is a complicated thing to explain without pictures, so I'd suggest you have a look at Wikipedia:
https://en.wikipedia.org/wiki/Call_stack
Which is a pretty good introduction (the actual operation and some of the problems stacks can cause gets a lot more complex than that if you aren't careful and you'll probably find that half of a whole book on memory management is devoted to it!)
In essence though, it's the compiler. And the CLR. And the actual microprocessor. But not the GC! :laugh: