In C, programmers totally control allocation and deallocation of dynamically created objects. And if a programmer does not destroy objects, memory leak happens in C,
Java does automatic Garbage collection. However there can be situations where garbage collector does not collect objects because there are references to them. There might be situations where an application creates lots of objects and does not use them. Just because every objects has valid references, garbage collector in Java can’t destroys the objects. Such types of useless objects are called as Memory leaks. If allocated memory goes beyond limit, program will be terminated by rising OutOfMemoryError. Hence if an object is no longer required, it is highly recommended to make that object eligible for garbage collector. Otherwise We should use some tools that do memory management to identifies useless objects or memory leaks like:Â
- HP OVO
- HP J METER
- JProbe
- IBM Tivoli
Java
// Java Program to illustrate memory leaksimport java.util.Vector;public class MemoryLeaksDemo{Â Â Â Â public static void main(String[] args)Â Â Â Â {Â Â Â Â Â Â Â Â Vector v = new Vector(214444);Â Â Â Â Â Â Â Â Vector v1 = new Vector(214744444);Â Â Â Â Â Â Â Â Vector v2 = new Vector(214444);Â Â Â Â Â Â Â Â System.out.println("Memory Leaks");Â Â Â Â }} |
Output:Â
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space exceed
Â
