Garbage Collection in Java

In the Java programming language, dynamic allocation of objects is achieved using the new operator. An object once created uses some memory and the memory remains allocated till there are references for the use of the object.

When there are no references for an object, it is assumed to be no longer needed and the memory occupied by the object can be reclaimed. There is no explicit need to destroy an object as java handles the de-allocation automatically.

The technique that accomplishes this is known as Garbage Collection. Programs that do not de-allocate memory can eventually crash when there is no memory left in the system to allocate. These programs are said to have memory leaks

Garbage collection in java happens automatically during the lifetime of a java program, eliminating the need to de-allocate memory and avoiding memory leaks. 

In C language, it is the programmer’s responsibility to de-allocate memory allocated dynamically using free() function. This is where Java memory management leads. 

 All objects are created in Heap Section of memory. More on this in a later tutorial.

Step 1) Copy the following code into a editor

class Student

{

int a;

int b;

  public void setData(int c,int d)

  {

    a=c;

    b=d;

  }

  public void showData()

  {

    System.out.println("Value of a = "+a);

    System.out.println("Value of b = "+b);

  }

  public static void main(String args[])

{

    Student s1 = new Student();

    Student s2 = new Student();

    s1.setData(1,2);

    s2.setData(3,4);

    s1.showData();

    s2.showData();

    //Student s3;

    //s3=s2;

    //s3.showData();

    //s2=null;

    //s3.showData();

    //s3=null;

    //s3.showData();

  }

}

Step 2) Save, Compile and Run the code. As shown in the diagram , two objects and two reference variables are created.

Step 3) Uncomment line # 20,21,22. Save , compile & run the code.

Step 4) As show in diagram below, two reference variables are pointing to the same object.

Step 5) Uncomment line # 23 & 24. Compile , Save & Run the code

Step 6) As show in diagram below , s2 becomes null , but s3 is still pointing to the object and is not eligible for java garbage collection.

Step 7) Uncomment line # 25 & 26 . Save , Compile & Run the Code

Step 8) At this point there are no references pointing to the object and becomes eligible for garbage collection. It will be removed from memory and there is no way of retrieving it back.

If you want to make your object eligible for Garbage Collection , assign its reference variable to null.