This week's giveaway is in the Programmer Certification (OCPJP) forum.
We're giving away four copies of Java Mock Exams (software) and have David Mayer on-line!
See this thread for details.
Win a copy of Java Mock Exams (software) this week in the Programmer Certification (OCPJP) forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Not Releasing Memory

 
Kenneth Winn
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have been profiling my applet using JProbe and have taken care
off all of the listeners (via weak references) and other references back to the applet so that there are no references from custom classes. In theory the applet should be released from the JVM. In appletviewer I selected 'reload' and that causes the stop, destroy and init methods to be called. I get a new instance of the main applet class but the origional one is still there. I see this via the profiler. Below is a list of objects that still have a reference to the origional instance of the main applet class. These are object that I cannot get to. They seem to be under the covers. I have included the list below:
<root> Native Stack
<root> Native Stack
EventQueueItem
EventQueueItem
Hashtable$Entry
LightweightDispatcher
MouseEvent
MouseEvent
OffScreenImage
OffScreenImage
SystemEventQueueUtilities$ComponentWorkRequest
WeakHashMap$WeakKey
Does this have to do with double bufferring?
thanks!
 
Happiness is not a goal ... it's a by-product of a life well lived - Eleanor Roosevelt. Tiny ad:
the new thread boost feature: great for the advertiser and smooth for the coderanch user
https://coderanch.com/t/674455/Thread-Boost-feature
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!