memory question

Hi @zal wel ,

Thanks for reaching out.

In your example:

HtmlButton bt = new HtmlButton();
bt = new HtmlButton();

What happens is that the first HtmlButton object is created and assigned to bt. Then, on the next line, bt is reassigned to a new HtmlButton instance.

Assuming no other references to the first object exist, it is no longer accessible in your code after the reassignment. At that point, it becomes eligible for garbage collection.

The .NET garbage collector will clean it up at a later time, based on its own internal scheduling, rather than immediately when the reference is lost.

Hope this helps! If my answer was helpful, I would greatly appreciate it if you could follow the instructions here so others with the same problem can benefit as well.

i have a question, does after garbage collection stays the first button in memory or will it be cleaned up i thought

The first button will be cleaned up by the Garbage Collection.

I understand that your app is the ASP.NET Web Forms. The ASP.NET Web Forms has another mechanism for memory management. After the last page event Page_Unload() the class representing the running page is disposed, and the page is unloaded from server memory.

HtmlButton bt = new HtmlButton(); bt = new HtmlButton();

After the second assignment, the first HtmlButton instance is no longer referenced by the local variable bt. If no other references to that first instance exist anywhere in the application (for example, it was never added to a control tree or stored in a field), it becomes unreachable.

In .NET, the garbage collector:

• Treats unreachable objects as garbage.
• Reclaims their memory during a future GC cycle.

So, assuming there are no other references, the first HtmlButton will be eligible for collection and its memory will eventually be freed by the GC. It is not freed immediately at the assignment; it is freed when the GC next runs and detects it as unreachable.

References:

• Fundamentals of garbage collection
• Automatic Memory Management