Why doesn't the .NET runtime offer deterministic destruction
- 1 Answers
- 1628 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 entity sql?
How does servicing work for the .net framework 3.0? If I install the .net framework 3.0, can I get service updates for the .net framework 2.0?
How do you handle variable number of segments in a route definition?
What are the sub types of ActionResult?
What is .net architecture and framework?
What is viewdata?
explain what does .edmx file contains?
What is stateless model?
Is .net core faster than .net framework?
What are the 2 popular asp.net mvc view engines?
If we write any code for DataGrid methods, what is the access specifier used for that methods in the code behind file and why?
Is .net core replacing .net framework?
How to answer for project questions..?
What are Validation Annotations?
What are the components required to create a route in ASP.Net MVC?
