Interested to Buy Any Domain ? << Click Here >> for more details...
Why doesn't the .NET runtime offer deterministic destruction
- 1 Answers
- 1962 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 advantages of asp.net mvc?
Give an example for authorization filters in an asp.net mvc application?
Can you explain renderbody and renderpage in asp.net mvc?
Will the name change be reflected in any of the existing .net framework 2.0 apis, assemblies, or namespaces?
Difference between manifest , metadata?
3 Answers Soma Technology, TCS,
What does assert() method do?
1 Answers MCN Solutions, Siebel Systems,
Can two application one using private assembly and other using Shared assembly be stated as a side-by-side executables?
What is Partial Assembly References?
What is difference between html.beginform and ajax.beginform?
How does work clr?
In Server how to check whether model has error or not in ASP.Net MVC
Is .NET a runtime service or a development platform?
Dot Net Framework 
