Why doesn't the .NET runtime offer deterministic destruction
- 1 Answers
- 1219 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 |
Explain what languages does the .net framework support?
Iam using an asp.net application . i want to update one of my table in database at 4pm every day how it is possible.
Name a few different return types of a controller action method?
what is client wins and store wins mode in entity framework concurrency?
How to use multiple submit buttons in asp.net mvc?
What are html helpers in asp.net mvc?
js fn to go to the particular page when enter is clicked
What are the options can be configured in AJAX helpers?
Changes to which portion of version number indicates an incompatible change
How we can multiple submit buttons in ASP.Net MVC
How do I use partial view?
What is Globalizationa and Localization
Dot Net Framework 
