Why doesn't the .NET runtime offer deterministic destruction
- 1 Answers
- 1200 Views
- I also Faced
- E-Mail Answers
Answer / 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 |
What is namespace used for loading assemblies at run time and name the methods?
How to Create an Intranet Site Using ASP.NET MVC?
What are multicast delegates ? give me an example
explain lazy loading, eager loading, and explicit loading?
Explain what languages does the .net framework support?
what is Assemble
Is .NET a runtime service or a development platform?
Explain the advantages of dependency injection (di) in asp.net mvc?
How do you convert a string into an integer in .NET
Name a few different return types of a controller action method?
What are the advantages of asp.net mvc?
Can we create the web service in windows application?
Dot Net Framework 
