Bug#453072: marked as done (gcj-4.2: Java processes are memory hogs on amd64)
Your message dated Sun, 17 May 2009 10:49:16 +0200
with message-id <4A0FCF8C.3060507@debian.org>
and subject line gcj-4.2 removed from unstable, closing bug reports
has caused the Debian Bug report #453072,
regarding gcj-4.2: Java processes are memory hogs on amd64
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
453072: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=453072
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: gcj-4.2: Java processes are memory hogs on amd64
- From: Daniel Schepler <schepler@math.unipd.it>
- Date: Mon, 26 Nov 2007 23:47:07 -0500
- Message-id: <200711262347.11100.schepler@math.unipd.it>
Package: gcj-4.2
Version: 4.2.2-3
Severity: important
X-Debbugs-CC: debian-glibc@lists.debian.org
It appears that the bug making gcj-4.2 based Java processes consume insane
amounts of memory on amd64 is still there. For example, trying to build
checkstyle under pbuilder, I watched the `java' process grow to over 4G
virtual memory before I had to kill it.
Cc to debian-glibc because as I recall, the bug was previously worked around
in glibc, but it seems not to be any more since version 2.7-1.
--
Daniel Schepler
--- End Message ---
--- Begin Message ---
gcj-4.2 removed from unstable, closing bug reports; these should be fixed in
gcj-4.4.
--- End Message ---
Reply to: