Interested to Buy Any Domain ? << Click Here >> for more details...
Why doesn't the .NET runtime offer deterministic destruction
- 1 Answers
- 1963 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
what is lazy loading in entity framework?
What is connected scenario? : Entity framework
what is entity graph in entity framework?
What is the use of razor view engine?
what is complex type?
Explain unit test done by tester on development team?
The order of the filters that get executed, if the multiple filters are implemented?
why DotNetFramework is included in building a software
How to Redirect Tracing to a File
What is ViewData and TempData in ASP.Net MVC?
Can I remove .net framework?
What is difference between razor and web form engine?
explain what is ado.net entity framework?
What are Model Binders in ASP.Net MVC?
mention what is code first approach and model first approach in entity framework?
