Is it true that objects don't always get destroyed immediately when the last reference goes away?



Is it true that objects don't always get destroyed immediately when the last reference goes awa..

Answer / Basant Yadav

In .NET, objects are not automatically destroyed when their last reference is removed. Instead, they remain in memory until garbage collection occurs. This behavior helps prevent excessive memory allocation and deallocation during runtime.

Is This Answer Correct ?    0 Yes 0 No

Post New Answer

More Dot Net General Interview Questions

What are the core differences between .NET Languages ?

1 Answers   TCS,


What tools can I use to develop .net applications?

1 Answers  


What is the use of immutability?

1 Answers  


How is a property designated as read-only?

2 Answers   Siebel Systems,


Explain how does assembly versioning work?

1 Answers  


When we use windows api in .net is it managed or unmanaged code?

1 Answers  


Is it true that objects don't always get destroyed immediately when the last reference goes away?

1 Answers  


I was working for software company frm 2005 to 2009. I left job due to recession.I was jobless till dec 09 then i got job in bpo and i am not knowing what to do as my professional experience is with software.give me any suggestion.

1 Answers  


What are object pooling and connection pooling and difference?

3 Answers   TCS,


Differences between namespace, class, assembly?

1 Answers  


What is multiThreading in .NET?

1 Answers  


What is assemblies in .net?

1 Answers  


Categories