Why doesn't the .NET runtime offer deterministic destruction
Answer Posted / 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 |
Post New Answer View All Answers
Where are the routing rules defined in an asp.net mvc application?
I want to fetch data from datareader. i have three tables in datareader. i want to bind my two table with datagrid, then i want to fetch a value from my third table. do u have any idea pls help me. we use dr.nextresult() for multiple tables.
How to bind table colum with gridview column?
What operating systems will the .net framework 3.0 be available for?
Will there be a .net compact framework 3.0 release with release of .net framework 3.0?
Is http stateful or stateless?
Briefly describe the roles of clr in .net framework?
Explain what is asp.net mvc?
Can you explain model, controller and view in mvc?
What is main objective of asp.net mvc 4 or what is new in mvc4 ?
What is a model in programming?
What is the use of razor view engine?
List out few different return types of a controller action method?
How to make sure Client Validation is enabled in ASP.Net MVC
Can you explain renderbody and renderpage in asp.net mvc?