Why doesn't the .NET runtime offer deterministic destruction
- 1 Answers
- 1188 Views
- I also Faced
- E-Mail Answers
Answer Posted / kirti
Because of the garbage collection algorithm. The .NET garbage collector works by periodically running through a list of all the objects that are currently being referenced by an application. All the objects that it doesn't find during this search are ready to be destroyed and the memory reclaimed. The implication of this algorithm is that the runtime doesn't get notified immediately when the final reference on an object goes away - it only finds out during the next sweep of the heap.
Futhermore, this type of algorithm works best by performing the garbage collection sweep as rarely as possible. Normally heap exhaustion is the trigger for a collection sweep.
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
I have 2+ years of fake experience,actually i could not answer for project questions..?how can i answer please suggest me..?
What is the .net framework?
What is .net framework & its benefits?
What is associationset? : Entity framework
What is tempdata?
What is entity graph? : Entity framework
What are the components required to create a route in ASP.Net MVC?
What is Layout in ASP.Net MVC?
What is meant by domain model?
why DotNetFramework is included in building a software
What is the importance of NonActionAttribute?
what is linq to entities?
What is session state management?
mention in what all scenarios entity framework can be applicable?
What is route config?
