This is the mail archive of the java-discuss@sources.redhat.com mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: 'Needed to allocate blacklisted block at 0x829d000' ?????

To: Bryce McKinlay <bryce at albatross dot co dot nz>
Subject: Re: 'Needed to allocate blacklisted block at 0x829d000' ?????
From: Jeff Sturm <jeff dot sturm at appnet dot com>
Date: Mon, 22 Jan 2001 23:30:16 -0500
CC: Barnet Wagman <wagman at enteract dot com>, java-discuss at sources dot redhat dot com
References: <140D21516EC2D3119EE700902787664401E3A85D@hplex1.hpl.hp.com> <3A6CCCBF.EF91DAEE@enteract.com> <3A6CE641.400B75DE@albatross.co.nz>

Bryce McKinlay wrote:
> Running compiled code from gij shouldn't make it any slower - you can put your
> classes in a shared library and then use gij to run them. See libjava/NEWS for
> details about that.

Exactly.  Note that gij is always built, even for machines that don't
support the interpreter.

> Imposing a max heap size is more of a security measure to guard against runaway
> apps bringing your system to a crawl.

One might argue that it is a bug of Sun's VM that it imposes an upper
bound, especially such a small one.  I've been bitten by that more than
once.  (Curiously, the Exact VM never even throws
java.lang.OutOfMemoryError AFAICT... it just slowly grinds to a halt.)

Jeff

References:
- RE: 'Needed to allocate blacklisted block at 0x829d000' ?????
  - From: Boehm, Hans
- Re: 'Needed to allocate blacklisted block at 0x829d000' ?????
  - From: Barnet Wagman
- Re: 'Needed to allocate blacklisted block at 0x829d000' ?????
  - From: Bryce McKinlay

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]