You say you get a stack overflow ? is that stack overflow as in
java.lang.StackOverflowError ? That sounds impossible !!
This error is supposed to mean too many nested method calls, but
your program doesn't do any nested calls !
If this is what is happening, send me the class file
and I'll decomp
Nick Lawson wrote:
> Hi Crispin, How you doing?
Well!...
>
>
> Your original question never did get a satisfactory answer.
> However it's definitely not the same as Luigi's.
>
> Perhaps you could try the code below; on Suns Windows JDK1.2
> the total
> stays constant at 1m, and the free highwa
Hi Crispin, How you doing?
Your original question never did get a satisfactory answer.
However it's definitely not the same as Luigi's.
Perhaps you could try the code below; on Suns Windows JDK1.2
the total
stays constant at 1m, and the free highwater mark hovers
around 820k,
at least for the fi
Michael Sinz wrote:
> Actually, this code is a "problem" but the bug is in the test.
> Why? Well, you are never returning from the constructor and thus
> certain parts of the system are still locked (synchronized) which
> prevents some forms of GC.
>
thanks for the comments on synchronization o
Crispin Miller <[EMAIL PROTECTED]> writes:
> The same thing happens with a Thread.yield();
> (in pre1 and pre2)
>
> I've tried moving the yield statement around to no avail...
>
> import java.util.*;
> public class SBTest {
>public SBTest() {
> int i = 0;
> while(true) {
>
Jan-Henrik Haukeland wrote:
> A thight loop (without sleep or yield), like the one above, will not
> let the gc thread in on the party. That's the case if you run on a
> preemptive JVM (i.e. with green threads) with real time slicing
> (native threads) it'll work.
The same thing happens with a T
Crispin Miller <[EMAIL PROTECTED]> writes:
> I posted to the group recently with a very similar problem to Luigi's problem -
> I think there is a memory leak in StringBuffer somewhere: the following code
> slowly eats up memory (it doesn't on a Sun).
>
> (running on JDK1.2-pre1).
>
> import jav
I posted to the group recently with a very similar problem to Luigi's problem -
I think there is a memory leak in StringBuffer somewhere: the following code
slowly eats up memory (it doesn't on a Sun).
(running on JDK1.2-pre1).
import java.util.*;
public class SBTest {
public SBTest() {
Sorry about the syntax error: the options are different in different JDKs;
-Xmx32m is correct for Suns JDK 1.2.
Nick
Luigi Giuri wrote:
> At 11.21 12/07/99 +0100, Nick Lawson wrote:
> >In JDK 1.2 the default max heap size is 16 Mb - I can't remember what
> >it was in 1.1. Is this your problem ?
Larry Gates wrote:
> [SNIP]
> >
> >>You can specify a larger heap
> >>with the command line option -Xmx32m, for example.
> >
> >Right, there is only a little syntax error: the option is -mx32m.
>
> interesting feature. What is the rationale behind the idea of a heap
> size? Whynot just use wha
Larry Gates wrote:
>
> interesting feature. What is the rationale behind the idea of a heap
> size? Whynot just use whatever RAM is available?
>
> -Larry Gates
>
If you have a memory leak (I've experience some ugly ones), it just
crashes the VM instead of bringing your system to a crawl.
Na
Larry Gates writes:
> >>You can specify a larger heap
> >>with the command line option -Xmx32m, for example.
> >
> >Right, there is only a little syntax error: the option is -mx32m.
>
> interesting feature. What is the rationale behind the idea of a heap
> size? Whynot just use whatever
>
>
> The objective of this program is to fill the computer RAM and swap area but,
> suddendly, when it crashes with a java.lang.OutOfMemoryError there are
> 66000 KB of free RAM (on a 96MB computer).
>
> I tried the jdk117_v3, but I obtained the same result.
> I also turned off the JIT compile
>Date: Mon, 12 Jul 1999 13:12:45 +0200
>From: [EMAIL PROTECTED] (Luigi Giuri)
>At 11.21 12/07/99 +0100, Nick Lawson wrote:
>>In JDK 1.2 the default max heap size is 16 Mb - I can't remember what
>>it was in 1.1. Is this your problem ?
>
>Yes !!!
>
>>You can specify a larger heap
>>with the comm
At 11.21 12/07/99 +0100, Nick Lawson wrote:
>In JDK 1.2 the default max heap size is 16 Mb - I can't remember what
>it was in 1.1. Is this your problem ?
Yes !!!
>You can specify a larger heap
>with the command line option -Xmx32m, for example.
Right, there is only a little syntax error: the o
In JDK 1.2 the default max heap size is 16 Mb - I can't remember what
it was in 1.1. Is this your problem ? You can specify a larger heap
with the command line option -Xmx32m, for example.
Nick
Luigi Giuri wrote:
> I'm having a problem using jdk117_v1a + Apache-JServ-1.0b3.
>
> The problem is th
[EMAIL PROTECTED] (Luigi Giuri) writes:
> I'm having a problem using jdk117_v1a + Apache-JServ-1.0b3.
>
> The problem is that sometimes a java.lang.OutOfMemoryError occurs,
> so I need to restart the JVM.
You should upgrade to JServ 1.0, or the latest cvs release. There was
a bug in the LogWrit
17 matches
Mail list logo
