This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hi, I have a swing applet which is in a popup launched from a html parent window. I have issues when I close the applet and the parent page. Many time i still find memory lingering (java coffee cup icon is present and task manager shows the IEXPLORE running). I can understand that if the parent is used to navigate to another site and only the applet is closed I can have memory still not cleared. But some times after i launch both the pages , i close the parent and then i open a new iexplore. now if i close the applet popup i still have memory lingering although the parent and the child (pop-up) are closed. Is this an issue bcos of memory handling with my code (i set all allocated objects to null) or is this expected with Swing?
I think this behavior is expected, and it's not just because you are using Swing. The JVM does not give up memory it has allocated since it would waste precious CPU cycles to allocate it, free it, and the next time an applet is loaded re-allocate it. [ February 02, 2004: Message edited by: Joe Ess ]
Thanks Joe. I was under the same impression that its an expected performance. But if so I wonder why many applications developed dont cause much issues or why developers have no reservations using it. Performance centric applications might suffer due to this then.