That's expected behaviour. (Just to avoid interpretations that it is a GC
flaw.)
If people are having memory problems because they aren't telling their
long-lived objects when short-lived objects are no longer needed, well,
that's expected behaviour too.
-----Original Message-----
From: Christian Pesch <[EMAIL PROTECTED]>
To: Greg Munt <[EMAIL PROTECTED]>
Cc: Ginny Schmidt <[EMAIL PROTECTED]>; [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Monday, June 11, 2001 02:27
Subject: Re: Accessing shared memory in Java
Greg Munt schrieb:
> >> Calling System.gc() doesn't seem to help
> >> either.
> >
> >That's what I observed, too.
>
> Well, it wouldn't help. System.gc() is not guaranteed to do *anything* -
in
> the same manner that garbage collection is not guaranteed to happen, ever.
Thats the one point, the other is that even if a garbage collection is
running
(and one most VMs I've seen, it does on System.gc()) it would not remove
objects one does not need anymore, but which are still referenced but other
more long living objects.
--
Christian Pesch - Software Engineer
[EMAIL PROTECTED] - fon +49.40.325587.505 fax .999
CoreMedia AG - www.coremedia.com - 0700-COREMEDIA
Erste Brunnenstra�e 1, 20459 Hamburg, Germany
CoreMedia - Think ahead! We're there.
_______________________________________________
Swing mailing list
[EMAIL PROTECTED]
http://eos.dk/mailman/listinfo/swing
_______________________________________________
Swing mailing list
[EMAIL PROTECTED]
http://eos.dk/mailman/listinfo/swing
