This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
RE: Re[2]: GC Warning: Header allocation failed: Dropping block.
- From: "Boehm, Hans" <hans dot boehm at hp dot com>
- To: "Yura Smolsky" <info at altervision dot biz>
- Cc: <java at gcc dot gnu dot org>
- Date: Thu, 17 Feb 2005 13:27:23 -0800
- Subject: RE: Re[2]: GC Warning: Header allocation failed: Dropping block.
> Here is log produced with 'export GC_PRINT_STATS=1'
> See attached 'gc.log'.
I assume this is x86/Linux?
Gcj normally uses a collector that's configured to grow the
heap with sbrk. (We thought that had been changed. But it wasn't
really changed until two days ago.)
It may be that the heap is running into a thread stack, and hence
can't grow very much.
Running the program with GC_PRINT_ADDRESS_MAP might confirm
or refute this.
If my guess is correct, building the collector with -DUSE_MMAP
should help. (Checking out and building todays CVS sources should
do that, but may not be what you want.)
>
> Also I have tried 'export GC_FIND_LEAK=1'. It shows me
> these messages. Can you explain them?
You forgot to call GC_free() on all those Java objects :-) .
Seriously, this is not a useful option for Java programs. It was
meant to detect leaks in C programs.
Hans