views:

1280

answers:

2

I am using jProfiler to find memory leaks in a Java swing application. I have identified instances of a JFrame which keeps growing in count.

This frame is opened, and then closed.

Using jProfiler, and viewing the Paths to GC Root there is only one reference, 'JNI Global reference'.

What does this mean? Why is it hanging on to each instance of the frame?

+1  A: 

Wikipedia has a good overview of JNI, essentially it allows communication between Java and native operating system libraries writen in other languages. http://en.wikipedia.org/wiki/Java_Native_Interface

JNI global references are prone to memory leaks, as they are not automatically garbage collected, and the programmer must explicitly free them. If you are not writing any JNI code yourself, it is possible that the library you are using has a memory leak.

[edit] here is a bit more info on local vs. global references, and why global references are used (and how they should be freed) http://journals.ecs.soton.ac.uk/java/tutorial/native1.1/implementing/refs.html

Pete
+3  A: 

A JNI global reference is a reference from "native" code to a Java object managed by the Java garbage collector. Its purpose is to prevent collection of an object that is still in use by native code, but doesn't appear to have any live references in the Java code.

A JFrame is a java.awt.Window, and is associated with a "native" Window object. When you are completely finished with a particular JFrame instance, you should invoke its dispose() method to clean up.

I am not sure if any native code is creating a global reference to the JFrame, but it seems likely. If it does, this will prevent the JFrame from being garbage collected. If you are creating many Windows (or subclasses) and seeing that they are never collected, make sure that they are disposed.

erickson
If the code is only Java, this is the most likely explanation. I've had problems with global pointers but I've been working with JNI.
Mario Ortegón