Skip to main content

Garbage collection example

A Java program can request the underlying JVM to perform garbage collection by calling the gc() method of the System class.

Note that System.gc() is a request to the underlying JVM. Garbage collection may not always happen. Hence we cannot depend on this method, however we can use it to optimize performance, with the understanding that it may not work as desired on all JVM's.


Study the program shown below. It ilustrates how we can invoke the garbage collector from a Java program.

01 /** This program creates instances of Bag objects in a loop which will run 100000 times.
02  * Whenever the program is in a loop that is a multiple of 1000, it requests the JVM
03  * to start the garbage collector. We will see that the JVM may not always fulfill the
04  * request.
05  */
06 public class GarbageCollectionDemo {
07   public static void main(String args[]) {
08     //loop 10000 times
09     for(int i=0;i<10000;i++) {
10       //if this loop is a multiple of 1000, then request for garbage collection
11       if(i%1000 == 0) {
12         System.out.println("Requesting for garbage collection");
13         System.gc();
14       }
15       System.out.println("Creating bag " + i);
16       Bag b = new Bag(String.valueOf(i));
17     }
18   }
19 }
21 /** A placeholder object that is created in GarbageCollectionDemo
22  *
23  */
24 class Bag {
25   private String id;
26   public Bag(String id) {
27 = id;
28   }
30   /**We override the finalize method and put a print statement
31    * which will tell us when the object was garbage collected.
32    */
33   public void finalize() {
34     System.out.println("Garbage collecting bag " + id);
35   }
36 }

Here is the output of the program. Since the output was very large, I have truncated most parts (which have been shown as dots ...). As is shown, we request for garbage collection after creating 999 objects [line 11]. The JVM complies and garbage collects all unused objects. Also note that the garbage collector again starts reclaiming objects on line 32, even though the program has not specifically asked for it to do so. It may have done so either because it ran short of resources (but that seems unlikely because the garbage collector had just freed resources some time back), or it was run in the normal course of the garbage collection algorithm (this seems more likely).

Now this JVM is really well behaved, it fulfills all our garbage collection requests, but do not take this behavior for granted. All JVM's may not be as well mannered.

02 Requesting for garbage collection
03 Creating bag 0
04 Creating bag 1
05 Creating bag 2
06 Creating bag 3
07 Creating bag 4
08 Creating bag 5
09 ...
10 Creating bag 999
11 Requesting for garbage collection
12 Garbage collecting bag 999
13 Garbage collecting bag 998
14 Garbage collecting bag 997
15 Garbage collecting bag 996
16 Garbage collecting bag 995
17 ...
18 Garbage collecting bag 5
19 Garbage collecting bag 4
20 Garbage collecting bag 3
21 Garbage collecting bag 2
22 Garbage collecting bag 1
23 Garbage collecting bag 0
24 Creating bag 1000
25 Creating bag 1001
26 Creating bag 1002
27 Creating bag 1003
28 ...
29 Creating bag 1452
30 Creating bag 1453
31 Creating bag 1454
32 Garbage collecting bag 1454
33 Garbage collecting bag 1001
34 ...
35 Garbage collecting bag 1228
36 Garbage collecting bag 1226
37 Garbage collecting bag 1227
38 Creating bag 1455
39 Creating bag 1456
40 ...
41 Creating bag 1998
42 Creating bag 1999
43 Requesting for garbage collection
44 Garbage collecting bag 1999
45 Garbage collecting bag 1998
46 ...
47 Garbage collecting bag 1456
48 Garbage collecting bag 1455
49 Creating bag 2000
50 ...
51 Creating bag 2813
52 Creating bag 2814
53 Garbage collecting bag 2814
54 Garbage collecting bag 2000
55 Garbage collecting bag 2813
56 ...
57 Garbage collecting bag 2413
58 Garbage collecting bag 2401
59 ...
60 Garbage collecting bag 2407
61 Creating bag 2815
62 Creating bag 2816
63 Creating bag 2817
64 ...
65 ...
66 ...
67 Creating bag 9872
68 ...
69 Creating bag 9999


Popular posts from this blog

Five Reasons Why Your Product Needs an Awesome User Guide

Photo Credit: Peter Merholz ( Creative Commons 2.0 SA License ) A user guide is essentially a book-length document containing instructions for installing, using or troubleshooting a hardware or software product. A user guide can be very brief - for example, only 10 or 20 pages or it can be a full-length book of 200 pages or more. -- As engineers, we give a lot of importance to product design, architecture, code quality, and UX. However, when it comes to the user manual, we often only manage to pay lip service. This is not good. A usable manual is as important as usable software because it is the first line of help for the user and the first line of customer service for the organization. Any organization that prides itself on great customer service must have an awesome user manual for the product. In the spirit of listicles - here are at least five reasons why you should have an awesome user manual! Enhance User Satisfaction In my fourteen years as a

Inheritance vs. composition depending on how much is same and how much differs

I am reading the excellent Django book right now. In the 4th chapter on Django templates , there is an example of includes and inheritance in Django templates. Without going into details about Django templates, the include is very similar to composition where we can include the text of another template for evaluation. Inheritance in Django templates works in a way similar to object inheritance. Django templates can specify certain blocks which can be redefined in subtemplates. The subtemplates use the rest of the parent template as is. Now we have all learned that inheritance is used when we have a is-a relationship between classes, and composition is used when we have a contains-a relationship. This is absolutely right, but while reading about Django templates, I just realized another pattern in these relationships. This is really simple and perhaps many of you may have already have had this insight... We use inheritance when we want to allow reuse of the bulk of one object in other

Planning a User Guide - Part 3/5 - Co-ordinate the Team

Photo by  Helloquence  on  Unsplash This is the third post in a series of five posts on how to plan a user guide. In the first post , I wrote about how to conduct an audience analysis and the second post discussed how to define the overall scope of the manual. Once the overall scope of the user guide is defined, the next step is to coordinate the team that will work on creating the manual. A typical team will consist of the following roles. Many of these roles will be fulfilled by freelancers since they are one-off or intermittent work engagements. At the end of the article, I have provided a list of websites where you can find good freelancers. Creative Artist You'll need to work with a creative artist to design the cover page and any other images for the user guide. Most small to mid-sized companies don't have a dedicated creative artist on their rolls. But that's not a problem. There are several freelancing websites where you can work with great creative ar