Bug#433391: marked as done (gij-4.1: Runs out of memory)
Your message dated Fri, 27 Jul 2007 20:21:39 +0200
with message-id <20070727182139.GA32369@hall.aurel32.net>
and subject line gij-4.1: Runs out of memory
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: gij-4.1
Version: 4.1.2-12
Severity: serious
Hi,
I've just got several buildd logs where I get errors like this:
GC Warning: Repeated allocation of very large block (appr. size 524288000):
May lead to memory leak and poor performance.
GC Warning: Out of Memory! Returning NIL!
Logs for the following packages on amd64:
eclipse_3.2.2-2
libxerces2-java_2.9.0-1
libxalan2-java_2.7.0-5
The hosts this happened on has 2 GB of RAM and 4 GB of swap.
eclipse_3.2.2-1 build without problems about a month ago, which was with
gij-4.1_4.1.2-8.
Kurt
--- End Message ---
--- Begin Message ---
On Tue, Jul 24, 2007 at 09:00:12AM +0200, Matthias Klose wrote:
> severity 433391 grave
> clone 433391 -1
> reassign -1 glibc
> block 433391 by -1
> thanks
>
> Building gcj or gcc-snapshot on a system downgraded to glibc-2.5
> doesn't show the testsuite failures in libjava.
>
This is actually a bug in java's unwinder, the fix I commited is wrong.
I am therefore closing this bug, leaving the one on gcj opened.
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' aurel32@debian.org | aurelien@aurel32.net
`- people.debian.org/~aurel32 | www.aurel32.net
--- End Message ---
Reply to: