«

Hi,

I am using internal frame in my program. How can i free the memory it
used when i close and Internal frame ??

plz help.

regards,
Rajesh Rapaka.

"Rajesh.Rapaka" <> schreef in bericht
news: oups.com...
> Hi,
>
> I am using internal frame in my program. How can i free the memory it
> used when i close and Internal frame ??

Dispose and set references to null.

Hi Boudewijn,

I've done that. But no use. I've even tried gc() and freememory()
funtions. neither helped.

any other ideas??

regards
Rajesh Rapaka.

"Rajesh.Rapaka" <> wrote in message
news: oups.com...
> Hi Boudewijn,
>
> I've done that. But no use. I've even tried gc() and freememory()
> funtions. neither helped.
>
> any other ideas??
>
> regards
> Rajesh Rapaka.
>

Helped what?
Setting references to null does nothing more than set references to null -
don't be fooled by the ever dominant fallacies that exist out there.
Do you have a resource leak? Grab yourself a profiler and find it.

--
Tony Morris

JTiger Unit Test Framework for J2SE 1.5
http://www.jtiger.org/
Java Q&A (FAQ, Trivia)
http://qa.jtiger.org/
http://xdweb.net/~dibblego/

hi,

> Helped what?
Neither of the process helped in freeing the memory. I've set the
resources to null and garbage collected it. but this wouldnt help me in
freeing the memory. how can i free the memory?

regards
Rajesh Rapaka.

"Rajesh.Rapaka" <> wrote in message
news: oups.com...
> hi,
>
> > Helped what?
> Neither of the process helped in freeing the memory. I've set the
> resources to null and garbage collected it. but this wouldnt help me in
> freeing the memory. how can i free the memory?
>
> regards
> Rajesh Rapaka.
>

You can't set a resource to null, nor can you garbage collect it, so it
seems you have a few concepts to brush up on.
Grab yourself a profiler and get cracking - usually only takes 20-30 seconds
to diagnose the issue if it's easily produced.

--
Tony Morris

JTiger Unit Test Framework for J2SE 1.5
http://www.jtiger.org/
Java Q&A (FAQ, Trivia)
http://qa.jtiger.org/
http://xdweb.net/~dibblego/

> Neither of the process helped in freeing the memory. I've set the
> resources to null and garbage collected it. but this wouldnt help me in
> freeing the memory. how can i free the memory?

You simply cannot free memory 'by hand'. If you set references to
null, it just means the the garbage-collector COULD free the memory
if it wants to.

And even if you call the garbage-collector yourself, that's just
a SUGGESTION to the VM to run the garbage-collector.

In reality, the garbage-collector will only start to free memory
if the memory on the computer is starting to run out (!).

Rajesh.Rapaka wrote:
> Hi,
>
> I am using internal frame in my program. How can i free the memory it
> used when i close and Internal frame ??

Read about -XX:MinHeapFreeRatio=10 -XX:MaxHeapFreeRatio=10 and
then have a look at

http://www.ebi.ac.uk/Rebholz-srv/wha...onvinceGC.html

Harald.

On Wed, 20 Apr 2005, Rajesh.Rapaka wrote:

> hi,
>
> Neither of the process helped in freeing the memory. I've set the
> resources to null and garbage collected it. but this wouldnt help me in
> freeing the memory. how can i free the memory?

You cannot explicitly free memory in Java. You can set all references to
an object to null. If nothing is referencing the object that the garbage
collector SHOULD free the memory. If you want it to free immediately then
you can call System.gc(); and it might run the garbage collector right
away. Note that the API docs clear say that calling System.gc() SUGGESTS
that the JVM expend effort towards recycling ununsed objects.

Bottom line, you cannot guarantee that the system will reclaim the memory.

If you are getting OutOfMemoryExceptions and there are objects that you
believe have no references to them that are not getting freed then maybe
you have a memory leak. Google on "java memory leak" and you should find
some articles on it.

The most common problem is that you have a reference to the object and you
just don't realize it. For a large system it will tend to be a reference
to an object that has a reference to an object that has a reference to the
object you believe should be free. In other words, it is not always that
easy to spot.

--
Send e-mail to: darrell dot grainger at utoronto dot ca

On Wed, 20 Apr 2005 13:48:48 +0100, <> wrote:

> In reality, the garbage-collector will only start to free memory
> if the memory on the computer is starting to run out (!).

That's not true, it depends on the JVM implementation (the JVM spec. does
not define how a garbage collector should behave) and its configuration.
Generally the heap cannot grow beyond a pre-configured maximum (-Xmx on
Sun VMs) so it will not use all of the computer's memory (unless you have
configured the heap to be allowed to grow that big).

Sun's VMs will increase the heap size as required but never reduce it.
With this behaviour the heap size would rapidly hit the maximum permitted
if they didn't ever perform garbage collection before the limit is reached.

System.gc() doesn't guarantee garbage collection will be performed, but it
usually is performed when this call is made.


Dan.

--
Daniel Dyer
http://www.footballpredictions.net