>We also tried to call periodically System.gc() but it didn't
>produced any visible results so we aborted this approach.
The VM collects garbage regardless of whether you call System.gc() or
not, System.gc() only allows you to suggest to the VM when might be a
good time to run the garbage coll
Title: RE: garbage collection
Alex, IMHO it appears you have a memory leak that is not necessarily a
JVM issue.
But while we are on the GC topic:
Does the 1.4 JVM 'stop the world', or pause *all* threads
while it does a GC. This tends to have a negative impact on
real-time Ja
On 24 Jan 00, at 10:22, yangyuexiang wrote:
> Who can tell me how to detect the algorithm used in
> JVM for garbage collection?
The correct implementation is not specified and port dependant.
If your questions refers to finding out which algorithm is used in a
specific port, you will have to lo
Hi Daniel!
DPZ>How can I tell how much memory an object takes?
There is an article on www.javaworld.com about this topic (it's about clever
memory usage, I don't know the exact title, but there are'nt so many articles
to choose from). Depending on the VM, java.lang.Object takes some 20-30 bytes
I actually looked at that page. I saw known bugs, and skipped fix bugs
thinking it wouldn't apply. Also, that green color makes the entries very
hard to read on my LCD screen.
Anway, that did work around the problem. It behaves as expected now.
Thus spake Marc Slemko on Tue, 09 Nov 1999:
> O
On Tue, 9 Nov 1999, Daniel P. Zepeda wrote:
[...]
> Now in linux using the jdk1.2-pre_v2, the programs memory requirement
> grows without bound until it crashes my system. Sun's jdk doesn't do
> this. It settles in with about 10 megs in memory and 30 megs in swap and
> wil stay there all day. Th
