Memory leak in swing

**smeshram** · 12-07-2011, 08:27 PM

I am facing memory leak problem in my swing based application. After following a series of steps (after opening and closing same frame 10 - 15 times) application is throwing OOM exception on GUI. When I analyzed heap dump with EMA (eclipse memory analyzer) it is showing that the common point of accumulation is KeyboardManager which is holding the reference in the collection to the object on the frame which is not visible on GUI. Please help me who we can dereference all object from keyboard manager.

**KevinWorkman** · 12-07-2011, 08:29 PM

Chances are this is a memory leak in your code, not in Swing. Can you reproduce the problem with an SSCCE?

**smeshram** · 12-07-2011, 08:45 PM

Do u have any idea why keyboard manager is having reference to the closed frame?? I guess it is internally handle by swing when any component become invisible.

**KevinWorkman** · 12-07-2011, 08:47 PM

Without seeing an SSCCE, I have no idea why any of the code is doing anything.

**Fubarable** · 12-07-2011, 08:50 PM

This is a known issue associated with Swing's use of strong references when you want to use weak ones. There are work arounds to be found if you Google the terms -- java swing references memory strong weak --

**doWhile** · 12-07-2011, 09:42 PM

Originally Posted by Fubarable

This is a known issue associated with Swing's use of strong references when you want to use weak ones. There are work arounds to be found if you Google the terms -- java swing references memory strong weak --

Ironically, the first hit when I just did the search was this thread ;)