Article View: borland.public.jbuilder.java.swing
Article #12742Re: Memory Leaks Issues with Swing in JBuilder 2 - Help!
From: Richard Wilkman
Date: Tue, 10 Nov 1998 00:00
Date: Tue, 10 Nov 1998 00:00
77 lines
3313 bytes
3313 bytes
Guerry: I'd look at JProbe from KL. There are places deep in JFC that hold references. You can't get to those, so it's going to leak. There are some interesting reports in the BugParade that have some workarounds and explanations. You might want to see of those match. Much of this is being addressed in 1.2. Of course, this means deciding if the known bugs in JFC 1.03 and 1.1.6 are better then the unknown bugs in JDK 1.2 (plus the hassles with moving from "old" JFC to "new" JFC. -Rich Guerry A. Semones wrote: > > We are experiencing memory leak issues. > > We are using Swing 1.0.3 and JDK 1.1.6 with the latest JBuilder 2 > (upgraded). > > We have an application with three tabbed panes. > Each pane contains several panels with controls. From these panels, we > launch various pop-up jdialog windows containing panels with controls. > > Each time we pop up one of these windows and then exit that window, we > are not able to reclaim all of the memory. To cause this to happen, we > have tried the following: > > 1. overridden the dispose methods to: > 2. set objects to null > 3. remove listeners and set those listener objects to null > 4. requesting garbage collection all over the place with System.gc() > 5. anything else we could think of. > > We are getting memory back, but not all of it under all circumstances. > > One of the main things that is getting trapped are object arrays > that seem to be tied into Swing components (combos, etc.). > > Also, if we return to the screen we had built and disposed of before > GC happens, it looks like all of the original memory from the first > invocation gets trapped underneath the second invocation and never > gets freed, despite nulling, etc. > > If GC happens before the second invocation, we do pretty well. > > We're using JInsight and another profiler to look at memory usage. > > Help! Any suggestions are welcome, even if we seem to have tried them. > > Thanks in advance, > > Guerry > > -- > Guerry A. Semones guerry.semones@wwt.com > Chief Software Architect gsemones@primary.net > Internet Business Applications Team Leader (314) 919-1567 (w) > World Wide Technology, Inc. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Rich Wilkman Senior Quality Assurance Engineer Borland JBuilder Team If you see something that looks like an opinion up there, it's mine and mine alone. Mail sent to me from the newsgroups won't bounce but will be ignored. If I have time, I'll respond, but you have a better chance if you confine your posts to the newsgroups =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Technical Details
Message-ID:
<3648725C.DADAD29A@inprise.com>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<3647A5DA.FB0246ED@primary.net>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 111d45,eef8a9bb68be6bba X-Google-Attributes: gid111d45,public From: Richard Wilkman <rwilkman@inprise.com> Subject: Re: Memory Leaks Issues with Swing in JBuilder 2 - Help! Date: 1998/11/10 Message-ID: <3648725C.DADAD29A@inprise.com> X-Deja-AN: 410367123 Content-Transfer-Encoding: 7bit References: <3647A5DA.FB0246ED@primary.net> Content-Type: text/plain; charset=us-ascii Organization: Another Netscape Collabra Server User Mime-Version: 1.0 Newsgroups: borland.public.jbuilder.java.swing