From: Erik Groeneveld <erik@cq2.nl>
To: Andrew Haley <aph@redhat.com>
Cc: java@gcc.gnu.org
Subject: Re: GC leaks debugging
Date: Tue, 05 Apr 2011 06:50:00 -0000 [thread overview]
Message-ID: <BANLkTi=3oDzGN-GkWOcQfiESZoyxCCnntg@mail.gmail.com> (raw)
In-Reply-To: <4D9993D4.9040704@redhat.com>
[...]
>> Any real program produces so much blacklist messages that it hardly
>> runs. I'd like to investigate this or am I on the wrong track
>> completely?
>
> I think you are. The heap is small in this simple test case, so there
> are no real problems.
I will ignore this for now then.
> You need to find out what the real problem is. Find just one of those
> "need to allocate large block" messages, and find out why it is being
> called. I suspect that there is an actual bug that is causing the
> explosion and it can be found. Forget about 991 blacklist messages:
> not useful.
I have done many tests, with different programs, which all run
flawlessly on OpenJDK, but explode on GCJ. I have run some test last
night, and I'll see from the logs that the heap is 1 GB, while about
700 MB of it is free. Also it seems that the finalization table keeps
growing. I am running now, but later this day I'll post the log. (And
search the mail archives with a new keyword: finalization ;-)
> I'd have a look myself, but there is no way to duplicate your problem.
> BTW, is this on a 32-bit or 64-bit platform?
It is on 32-bit. On 64 bit, the blacklisting is not happening. But
the heap keeps exploding, so you are right, the problem probably lies
elsewhere.
(Although I still feel sorry for the poor GC on 32 bit systems ;-)
Thanks a lot.
Erik
next prev parent reply other threads:[~2011-04-05 6:50 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 8:39 Erik Groeneveld
2011-04-01 8:45 ` Andrew Haley
2011-04-01 9:03 ` Erik Groeneveld
2011-04-01 9:34 ` Andrew Haley
2011-04-02 0:27 ` Boehm, Hans
2011-04-02 9:39 ` Erik Groeneveld
2011-04-03 17:15 ` Erik Groeneveld
2011-04-03 18:00 ` Erik Groeneveld
2011-04-04 8:13 ` Andrew Haley
2011-04-04 8:53 ` Erik Groeneveld
2011-04-04 9:48 ` Andrew Haley
2011-04-05 4:44 ` Boehm, Hans
2011-04-05 8:58 ` Andrew Haley
2011-04-05 6:50 ` Erik Groeneveld [this message]
2011-04-05 9:02 ` Andrew Haley
2011-04-05 12:02 ` Erik Groeneveld
2011-04-05 12:55 ` Andrew Haley
2011-04-06 14:30 ` Erik Groeneveld
2011-04-06 18:33 ` Andrew Haley
2011-04-06 18:39 ` David Daney
2011-04-07 17:43 ` Erik Groeneveld
2011-04-08 8:12 ` Erik Groeneveld
2011-04-08 13:56 ` Andrew Haley
2011-04-08 15:35 ` David Daney
2011-04-08 15:53 ` Erik Groeneveld
2011-04-08 15:57 ` Andrew Haley
2011-04-08 15:48 ` Erik Groeneveld
2011-04-09 1:17 ` Boehm, Hans
2011-04-09 8:47 ` Andrew Haley
2011-04-09 10:56 ` Erik Groeneveld
2011-04-10 11:03 ` Erik Groeneveld
2011-04-12 18:43 ` Erik Groeneveld
2011-04-13 8:11 ` Andrew Haley
2011-04-13 12:11 ` Bryce McKinlay
2011-04-13 14:27 ` Andrew Haley
2011-04-14 8:36 ` Erik Groeneveld
2011-04-14 8:43 ` Andrew Haley
2011-04-14 10:02 ` Erik Groeneveld
2011-04-14 10:50 ` Andrew Haley
2011-04-15 7:32 ` Erik J Groeneveld
2011-04-01 17:41 ` David Daney
2011-04-02 16:21 ` Erik Groeneveld
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTi=3oDzGN-GkWOcQfiESZoyxCCnntg@mail.gmail.com' \
--to=erik@cq2.nl \
--cc=aph@redhat.com \
--cc=java@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).