Solve : Garbage Collection?

1.	Solve : Garbage Collection?
Answer» The garbage collection is an automatic memory management scheme employed by the .net framework is called garbage collection. The garbage collector is continuously tracing out of scope objects and identify that no longer have references. Because the garbage collection is always running . We do not have to explicitly distroy the objects. It will automatically cleaned when we are finishing working with them.what? Please explain your problem in more detail.More detail: detail detail detail detail detail detail detail enough?Pardon my error. I thought since dhananjay was the only one in this THREAD who had a problem, that everyone would assume I was directing the question at him. I'll try again. Dhananjay, can you please explain your problem in more detail? Also, look here before posting. You didn't take my post seriously, did you? Nominated for Post of the Month... 13 Days left to Vote.He just edited his first post. Dhananjay, do you have a question? Quote from: dhananjay on SEPTEMBER 16, 2008, 04:30:44 AM The garbage collection is an automatic memory management scheme employed by the .net framework is called garbage collection. The garbage collector is continuously tracing out of scope objects and identify that no longer have references. Because the garbage collection is always running . We do not have to explicitly distroy the objects. It will automatically cleaned when we are finishing working with them. well thank goodness he cleared up the difference between REFERENCE counting and garbage collection. I for one missed the million or so mentions of the differences in the documentation, so it's a good thing I found this post that has almost nothing to do with windows (Java has garbage collection to, and it RUNS on a lot of OS systems), and should have rather have been placed in the Programming forum- to be met with the same type of confusion.I believe the original poster is just WANTING to verify that if he does nothing with the objects no longer being used, the "garbage collector" will remove them for him. Let's see how he responds... Quote from: Aegis on September 27, 2008, 12:32:17 AM I believe the original poster is just wanting to verify that if he does nothing with the objects no longer being used, the "garbage collector" will remove them for him. Well, I'll tell him this then- they don't call it a garbage collector for leaking memory!

Answer»

The garbage collection is an automatic memory management scheme employed by the .net framework is called garbage collection. The garbage collector is continuously tracing out of scope objects and identify that no longer have references.

Because the garbage collection is always running . We do not have to explicitly distroy the objects. It will automatically cleaned when we are finishing working with them.what? Please explain your problem in more detail.More detail:

detail
detail
detail
detail
detail
detail
detail

enough?Pardon my error. I thought since dhananjay was the only one in this THREAD who had a problem, that everyone would assume I was directing the question at him. I'll try again.

Dhananjay, can you please explain your problem in more detail? Also, look here before posting.

You didn't take my post seriously, did you? Nominated for Post of the Month...
13 Days left to Vote.He just edited his first post.

Dhananjay, do you have a question? Quote from: dhananjay on SEPTEMBER 16, 2008, 04:30:44 AM

The garbage collection is an automatic memory management scheme employed by the .net framework is called garbage collection. The garbage collector is continuously tracing out of scope objects and identify that no longer have references.

Because the garbage collection is always running . We do not have to explicitly distroy the objects. It will automatically cleaned when we are finishing working with them.

well thank goodness he cleared up the difference between REFERENCE counting and garbage collection. I for one missed the million or so mentions of the differences in the documentation, so it's a good thing I found this post that has almost nothing to do with windows (Java has garbage collection to, and it RUNS on a lot of OS systems), and should have rather have been placed in the Programming forum- to be met with the same type of confusion.I believe the original poster is just WANTING to verify that if he does nothing with the objects no longer being used, the "garbage collector" will remove them for him.

Let's see how he responds... Quote from: Aegis on September 27, 2008, 12:32:17 AM

I believe the original poster is just wanting to verify that if he does nothing with the objects no longer being used, the "garbage collector" will remove them for him.

Well, I'll tell him this then- they don't call it a garbage collector for leaking memory!

Solve : Garbage Collection?

Discussion

No Comment Found

Related InterviewSolutions

Reply to Comment