Interested to Buy Any Domain ? << Click Here >> for more details...
Why doesn't the .NET runtime offer deterministic destruction
- 1 Answers
- 1974 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 IL
What is the use of razor view engine?
what is linq to entities?
Why is XmlSerializer so slow
How to make sure Client Validation is enabled in ASP.Net MVC
what is model first approach?
what are abstract classes? what is overriding?
Why do you need to box a primitive variable
Types of assemblies that can be created in dotnet ?
what are background threads? give ex?
I couldnot answer for projects bcz i have 2+ fake experience.can you please tell me how to answer..?
How to ensure the credentials for WebService using Windows authentication
Dot Net Framework 
