Method and apparatus for determining leaks in a Java heap

Abstract

An improved method, apparatus, and computer instructions for identifying a memory leak in a heap. Prior to the start of the observation period, all live objects in the heap are identified to form a set of live objects by altering an indicator in the live objects. After running the system for the required amount of time or until completion of the event being monitored, the system is used to obtain the list of live objects without the altered indicator. Live objects without the altered indicators form the most likely objects associated with a memory leak.

Description

BACKGROUND OF THE INVENTION [0001] 1. Technical Field [0002] The present invention relates generally to an improved data processing system and in particular to a method and apparatus for processing data. Still more particularly, the present invention relates to a method, apparatus, and computer instructions for identifying memory leaks. [0003] 2. Description of Related Art [0004] Data storage components, variables, collections, and multi-dimensional collections are used throughout all computer applications. During the execution of an application, the contents of these types of data storage elements will change or evolve. These changes occur due to modifications or updates to the data. These changes may be made by user input or through programmatic means. [0005] In a Java virtual machine, a heap is a memory area, which contains all of the objects created by an application. During the course of executions, some objects may no longer be needed or used by an application. These types of ...

AI Technical Summary

Problems solved by technology

Even with memory recycling, memory leaks may occur.

A memory leak is a condition caused by a program that does not free up the extra memory allocated by that program.

When memory is allocated, but not deallocated, a memory leak occurs.

If too many memory leaks occur, these memory leaks can usurp all of memory and bring everything to a halt or slow the processing considerably.

However, program level memory leaks can still occur.

For example, programming errors can lead to object references still being held in a global data structure, which leads to reduced free space on the heap for allocating new objects.

Memory leaks in a Java heap are currently very difficult to identify or diagnose.

These types of memory leaks are especially difficult to determine or identify if the leak is intermittent or very slow.

In some cases, a memory leak in a Java heap in a production system may take many days to manifest.

These tools are all very invasive and require the use of the Java Virtual Machine Profiler Interface (JVMPI) to instrument the allocation path of the Java virtual machine (JVM) and to store information over time.

This technique is much too heavy of a weight to employ in a product environment over the period of many days.

Images