> > I'm unclear on just why a Java VM would get this. It seems that they > (most of them) pre-allocate a large chunk of memory (64 MB), and then > dole this out to the application as it's needed. But what happens > when that initial chunk is all used up? Doesn't it allocate more? > Perhaps, perhaps not. More importantly, if it can't/won't allocate > more memory, doesn't the application get some sort of error condition > that it can check? In C, malloc() would return NULL. I have no > idea what the Java equivalent of that is. But it's clear to me that > when the JVM runs out of memory, Freenet is *not* handling it > gracefully.
The Sun JVM at least has a default max heap size of 64mb. It does not allocate this at start, but grows up to this limit. Once its reached it doesnt get anymore though. This setting can be changed with -Xmx<n>mb. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20020904/ecb2c015/attachment.pgp>
