I have seen Sun's bug report 4267247 and various discussions on this matter but does anyone know the status of this or a workaround? Here's what I know so far: When you use dispose ( ) method on frames then only system resources used by that Frame are released. The frame itself is not destroyed , so all the member variables of that frame are still alive. The frame object will be destroyed only when it goes out of scope and Garbage Collector feels it should release the memory help up by that frame. Even if you run System.gc() it is just a hint to Garbage Collector to run . It is totally up to Garbage Collector when it release the memory used by frame. So System.gc() won't help. And finally, you know there is no user's control in Java Program how and when the memory will be freed, so you cannot do it explicitly. Maximum, you can do is you can set that frame to null. But even setting a frame to null doesn't help. I'm running as an applet over an intranet..and if the applet is kept up long enough, a person's computer is locked up. Not a good thing! Any suggestions would be welcomed. Thanks, -- Ginny Schmidt Email: [EMAIL PROTECTED] _______________________________________________ Swing mailing list [EMAIL PROTECTED] http://eos.dk/mailman/listinfo/swing
