Re: Remove JFrame from memory
On Friday, June 29, 2012 12:58:01 AM UTC-7, Jesper Johnsen wrote:
Thank you for a very good reply.
If the program doesn't use up memory for new objects, the memory it
already has is sufficient and there is no reason for the garbage
collector to run around trying to find more.
My program is just a sample, and I was just curious why, the object was not removed. B
The JFrame may or
may not have been collected; you cannot tell from outside Java.
As Lew also say I have free Heap space so my object is not GC'ed. and from the memory debugger I can see that my heap space is actually reduced when the object is disposed. So the code is working - and I learned something great
class MyFrame extends JFrame {
MyFrame(String title) {
super(title);
}
// I do not usually recommend implementing finalize(),
// but here we're just using it for exploration.
protected void finalize() throws Throwable {
try {
System.err.println("Finalizing " + this);
} finally {
super.finalize();
}
}
}
Thank you for this, I will try play with it in some of my larger applications.
Don't.
You almost never want to override 'finalize()'. To find out what lies outside
that "almost", read /Effective Java/ by Joshua Bloch.
Do not use 'finalize()' until you understand its dangers and its effects on GC.
For example, incorrect use of 'finalize()' overrides can increase the risk of
crashes. It does delay and can prevent the collection of dereferenced instances.
Do not use 'finalize()' lightly.
--
Lew