Return to Answer

because the method Instantiate has side effects, It will create a gameobject on your scene. You can check them in the hierarchy tab.

So you don't actually lose the reference to the button component. The local variables are indeed discarded, but that's okay.

By the way, some statements in the post are not quite correct:

It's said that local variable is deallocated (lost) when leaving the countaining method. 

Firstly, when does the 'deallocating' occur? It's not 'when leaving the countaining method' but 'when leaving it's scope'.

And do all local variable is deallocated or lost directly? It depends on the type of variable.

There are two kinds of types in C#: reference types and value types. Variables of reference types store references to their data (objects), while variables of value types directly contain their data. They are stored in Heap and Stack Memory respectively.

When a value type variable is discarded, it will be recycled directly. If a reference type variable is discarded, it will keep in memory. If it is not referenced by any object in the next garbage collection, it will be deleted.(mark-and-sweep-algorithm) The variable holding its reference is discarded, but the actual object is still in heap memory. If other objects still hold its reference then it won't be cleaned up.

Because the method Instantiate has side effects, It will create a game object on your scene. You can check the hierarchy tab to find it.

So you don't actually lose the button component. The local variable holding a reference to it is indeed discarded, but that's okay, because the scene hierarchy still holds a reference to it (you can access it via FindObjectsOfType() or methods that traverse the scene hierarchy).

By the way, some statements in the post are not quite correct:

It's said that local variable is deallocated (lost) when leaving the containing method.

Firstly, when does the 'deallocating' occur? It's not 'when leaving the containing method' but 'when leaving it's scope'.

And are all local variables deallocated or lost directly? It depends on the type of variable.

There are two kinds of types in C#: reference types and value types. Variables of reference types store references to their data (objects), while variables of value types directly contain their data. They are stored in Heap and Stack Memory respectively.

When a value type variable is discarded, it will be recycled directly. If a reference type variable is discarded, the data it referenced will still persist in memory. If it is not referenced by any object in the next garbage collection pass, it will be deleted.(Mark-and-sweep-algorithm) The variable holding its reference is discarded, but the actual object is still in heap memory. If other objects still hold references to it, then it won't be cleaned up.

because the method Instantiate has side effects, It will create a gameobject on your scene. You can check them in the hierarchy tab.

So you don't actually lose the reference to the button component. The local variables are indeed discarded, but that's okay.

By the way, some statements in the post are not quite correct:

It's said that local variable is deallocated (lost) when leaving the countaining method. 

Firstly, when does the 'deallocating' occur? It's not 'when leaving the countaining method' but 'when leaving it's scope'.

And do all local variable is deallocated or lost directly? It depends on the type of variable.

There are two kinds of types in C#: reference types and value types. Variables of reference types store references to their data (objects), while variables of value types directly contain their data. They are stored in Stack and Heap Memory respectively.

When a value type variable is discarded, it will be recycled directly. If a reference type variable is discarded, it will decrement the reference count. They are managed by garbage collection. The variable holding its reference is discarded, but the actual object is still in memory. If other objects still hold its reference then it won't be cleaned up.

because the method Instantiate has side effects, It will create a gameobject on your scene. You can check them in the hierarchy tab.

So you don't actually lose the reference to the button component. The local variables are indeed discarded, but that's okay.

By the way, some statements in the post are not quite correct:

It's said that local variable is deallocated (lost) when leaving the countaining method. 

Firstly, when does the 'deallocating' occur? It's not 'when leaving the countaining method' but 'when leaving it's scope'.

And do all local variable is deallocated or lost directly? It depends on the type of variable.

There are two kinds of types in C#: reference types and value types. Variables of reference types store references to their data (objects), while variables of value types directly contain their data. They are stored in Heap and Stack Memory respectively.

When a value type variable is discarded, it will be recycled directly. If a reference type variable is discarded, it will keep in memory. If it is not referenced by any object in the next garbage collection, it will be deleted.(mark-and-sweep-algorithm) The variable holding its reference is discarded, but the actual object is still in heap memory. If other objects still hold its reference then it won't be cleaned up.

because the method Instantiate has side effects, It will create a gameobject on your scene. You can check them in the hierarchy tab.

So you don't actually lose the reference to the button component. The local variables are indeed discarded, but that's okay.

because the method Instantiate has side effects, It will create a gameobject on your scene. You can check them in the hierarchy tab.

So you don't actually lose the reference to the button component. The local variables are indeed discarded, but that's okay.

By the way, some statements in the post are not quite correct:

It's said that local variable is deallocated (lost) when leaving the countaining method. 

Firstly, when does the 'deallocating' occur? It's not 'when leaving the countaining method' but 'when leaving it's scope'.

And do all local variable is deallocated or lost directly? It depends on the type of variable.

There are two kinds of types in C#: reference types and value types. Variables of reference types store references to their data (objects), while variables of value types directly contain their data. They are stored in Stack and Heap Memory respectively.

When a value type variable is discarded, it will be recycled directly. If a reference type variable is discarded, it will decrement the reference count. They are managed by garbage collection. The variable holding its reference is discarded, but the actual object is still in memory. If other objects still hold its reference then it won't be cleaned up.