Deallocation memory

Vineet Kumar Saini

15y10.6k.NET

Hi..

I want to know name of keyword ,which is used for deallocation memory in .NET ?

Thanks...

9 Replies

Know the answer? Post it — somebody with the same question will find it here.

Datta Kharad15y ago
Accepted answer
Hi..

1) GC.Collect():-
The C# language is a garbage-collected language, which means that memory that is no longer referenced by your program will be reclaimed and can later be reused. With the GC.Collect method, you can force a garbage collection to occur at any time. GC.Collect method is not useful because it often has little benefit and might even reduce performance, while increasing complexity and causing you headaches.

2) Dispose() :- Dispose method is used to release unmanaged resources when unmanaged resources are no longer in use.And Programmers should keep in mind at the time of codeing(using dispose method) for best memory management.
0
Vineet Kumar Saini15y ago
Hi Arti Ji..

Please don't copy answer of anyone.If you want give a answer of any question then you can create in your mind.

Thanks...
0
Aarti15y ago
Hi Vineet,

To Deallocate memory in Dot Net,wwe first call GC.Collect() then Dispose() method.

1) GC.Collect():-
The C# language is a garbage-collected language, which means that memory that is no longer referenced by your program will be reclaimed and can later be reused. With the GC.Collect method, you can force a garbage collection to occur at any time. GC.Collect method is not useful because it often has little benefit and might even reduce performance, while increasing complexity and causing you headaches.

2) Dispose() :- Dispose method is used to release unmanaged resources when unmanaged resources are no longer in use.And Programmers should keep in mind at the time of codeing(using dispose method) for best memory management.

Thanks.
0
dev 015y ago
Hi Vineet ,

The let us Keyowrd in .net 4.0 is Using for deallocate the memory , so we dont need to call dispose function, this Using keyword deallocate memory , in short it calls garbage collector.

Hope this will help you.

Thanks
0
Manoj Sevda15y ago
Dear Vineet,

.NET uses a garbage collector to clean up memory on the heap. With each collection cycle, variables and objects that are no longer reachable by code are discarded automatically. If You want to clean up memory explicitly then you can use using method. For example

using (MyObject myObject = new MyObject())
{
// use your object
}

in this process your MyObject have to inherited with Idisposable Interface, which is explicitly dispose the object when object scope was ended.

In Other Words..

If the object implements IDisposable, then you need to call Dispose. For example, if you go new FileStream(...), then the FileStream needs to be disposed, since it implements IDisposable. I would suggest you read up on the using construct in C# which makes it easier to handle IDisposable objects.

Not really, 99.99% of the time, the garbage collector will know when the best time to run is. It's one of those, "you'll know when you need it" kind of situations.

When the object containing the event is no longer referenced, then logically any object references contained in the event are also no longer referenced and will be available to be collected. /
0
Amit Maheshwari15y ago
Hello vineet,

i think you should follow that link which is given below,

http://msdn.microsoft.com/en-us/library/aa691138(VS.71).aspx
0
Sam Hobbs15y ago
It is critical to understand that .Net is designed so that you do nt need to deallocate memory explicitly; usually it is a mistake to try to do that. So if you are experienced with C++ you will be frustrated because destruction in C# is quite imprecise compared to C++. Usually we can and should just ignore the need to destroy an object and instead assume it will be done properly.
0
Vulpes15y ago
The nearest we have to a keyword for deallocating memory in C# is 'using' in the context of the 'using' statement.

This is used to release unmanaged resources which an object implementing IDisposable was using by implicitly calling its Dispose() method when the using statement ends.

However, this doesn't reclaim the managed memory used by the object which (as long as there are no further references to it) will be reclaimed by the garbage collector in due course. The GC.Collect method which Javeed mentioned causes an immediate garbage collection of all unused objects (or a generation of such objects).

If the object has a destructor, the GC will call this first before the reclamation takes place.
0
Javeed M Shaikh15y ago
is this what you are looking for...

GC.Collect();
GC.WaitForPendingFinalizers();
0