Interested to Buy Any Domain ? << Click Here >> for more details...
Why doesn't the .NET runtime offer deterministic destruction
- 1 Answers
- 2045 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 difference b/w .net 1.1 and .net 2.0. I need Answer in c# , asp.net and ado.net Level.Like c#1.1 and c#.1.1 , ado.net1.1 and ado.net2.0 and asp.net1.1 and asp.net2.0
about triggers?
What are the types of authentication in .net
Can a view be shared across multiple controllers? If yes, how we can do that?
What is mvc entity framework?
Why string are called Immutable data Type
Can I look at the IL for an assembly
Can I add asp.net mvc testcases in visual studio express?
What is viewdata?
How we can add the css in mvc?
Which is the default http method for an action method?
mention what is the key advantage of using entity framework or ef?
Dot Net Framework 
