Interested to Buy Any Domain ? << Click Here >> for more details...
Why doesn't the .NET runtime offer deterministic destruction
- 1 Answers
- 2057 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 are the derived classes from xmlReader and xmlWriter
creating crystal reports in asp.net & vb.net
What is the difference between model view and controller?
What's different about namespace declaration when comparing that to package declaration in Java ?
Requirement is: try { \\SQL Query } catch(Exception i) { print a } catch(SQLQueryException e) { \\SQL Query } Qu)I Got Exception in "try" block. Which "catch" statement (i.e. 1st catch or 2nd catch ) catches the exception and Why???
What is action methods in web api?
I can't be bothered with all this CAS stuff. Can I turn it off
What is renderbody?
What are the 2 ways of adding constraints to a route?
Can we add constraints to the route? If yes, explain how we can do it?
What is conceptual model? : Entity framework
How to make sure Client Validation is enabled in ASP.Net MVC
Dot Net Framework 
