Object being created and destroyed in a forloop

Erik Movsesyan

4y1.3kC#

Hello, I have the following code here:

class uno {
    int x;

    public uno(int i) {
        x = i;
    }

    public void gen(int h) {
        new uno(h);
    }
}

class dos {
    public static void Main() {
        uno jj = new(0);

        for (int i=1;i<=10;i++) {
            jj.gen(i);
        }
    }
}

I read in the following book: memberfiles.freewebs.com/02/83/78118302/documents/McGraw.Hill.CSharp.4.0.The.Complete.Reference.Apr.2010.pdf

pages 134-135

that the gen(int i); method creates and destroys objects immediately.

Does this mean that in a loop whwnwver you create objects after each itertion, the objetc is created and detroyed immediately?
If yes, then how is that object destroyed(obviously not by the GC as It says that the object is destroyed IMMEDIATELY)?

4 Replies

Know the answer? Post it — somebody with the same question will find it here.

Santosh Karanam4y ago
For loop is considered as a execution block.
Any variables decalred inside this block are considered to be within this scope.
When execution goes out of this block then scoped variables are removed from stack memory.
This is true for each loop of for each bock.
Once the variables are removed from stack memory they are in accessible by the code anymore, so technically they are destroyed. But the heap memory alocated only gets cleaned when Garbage collector cleans it. So yes for each for loop varibale created within are created and deleted immediatly. The forloog variable for(int i;i<10;i++) is deleted (removed from stack) when for loop ends.

CHeck these articles in c# corner to get idea on stack and heam memory allocation and deallocation
1. https://www.c-sharpcorner.com/article/stack-vs-heap-memory-c-sharp/.
2. https://www.c-sharpcorner.com/article/C-Sharp-heaping-vs-stacking-in-net-part-i/
+4
Sachin Singh4y ago
when an object goes out of scope meaning when method execution completes the object goes for Garbage collection, but it is not destroyed immediately.
There are 3 generations of GC, so first, it goes to Gen1 then Gen2, and then it is destroyed. Also, GC collects unused and unreferenced objects randomly, meaning, over a random period of time.
+3
Muhammad Imran Ansari4y ago
In for loop, when call gen(i) method it initialize the object and inside gen() menthod, an object is created and destruped on leaving method. On leaving object finalizer is called and destroy the object and claim for GC.

I don't think you should rely on garbage collectors in this way, this is performing by Objects finalizer. The Objects Finalize method is used to perform cleanup operations on unmanaged resources held by the current object before the object is destroyed before it is reclaimed by garbage collection.
Once there are no more references to a given object, that object becomes eligible for garbage collection (GC) should the need arise. Whenever the GC decides it needs to reclaim the space your no-longer-referenced object, that's when the objects finalizer will be called.
+4
Rajanikant Hawaldar4y ago
please read, generation of garbage collector in c#. those objects become dead objects when come out of method, these dead objects will be garbage collected automatically by GC when your application needs free memory
+4