Interested to Buy Any Domain ? << Click Here >> for more details...
Why doesn't the .NET runtime offer deterministic destruction
- 1 Answers
- 2142 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 |
How OS come to know whether to load the .net framework when we run an .exe created using .Net framework?
Can you set the unlimited length for "maxjsonlength" property in config?
I have 2+ years of fake experience,actually i could not answer for project questions..?how can i answer please suggest me..?
im software developer (.net). i goth1b (usa )appointment 30th of this month . chennai people asking responsbilities .can anyone wht responsbilities i need say . plz help me
Can we add constraints to the route? If yes, explain how we can do it?
What is viewbag title?
How the ‘page lifecycle’ of ASP.Net MVC does works?
Why is entity framework used?
Do I need microsoft .net framework?
What is "out" parameter how it is used in methods?
When do you absolutely have to declare a class as abstract
What is Peek method in Tempdata in ASP.Net MVC?
Dot Net Framework 
