From: "Boehm, Hans" <hans.boehm@hp.com>
To: Andrew Haley <aph@redhat.com>, "java@gcc.gnu.org" <java@gcc.gnu.org>
Subject: RE: GC leaks debugging
Date: Sat, 02 Apr 2011 00:27:00 -0000 [thread overview]
Message-ID: <238A96A773B3934685A7269CC8A8D04272EFEFD5C3@GVW0436EXB.americas.hpqcorp.net> (raw)
In-Reply-To: <4D959C24.8030408@redhat.com>
> -----Original Message-----
> From: java-owner@gcc.gnu.org Andrew Haley
> Sent: Friday, April 01, 2011 2:34 AM
> To: java@gcc.gnu.org
> Subject: Re: GC leaks debugging
>
> On 04/01/2011 10:02 AM, Erik Groeneveld wrote:
> > On Fri, Apr 1, 2011 at 10:45, Andrew Haley <aph@redhat.com> wrote:
> >> On 01/04/11 09:39, Erik Groeneveld wrote:
> >>> From reading about the
> >>> GC, I understand that the GC knows what is a pointer and what not
> >>> because there is type information associated with the Java objects.
> >>> So I'd expect no black-listing at all. It that a right
> observation?
> >>
> >> No. Objects are scanned precisely, but the stack is not.
> >
> > Thanks. I think I can rule the stack out by reviewing/adapting my
> > test program. I'll do that first.
> >
> >> Also, depending
> >> on your compilation options, the data segments of your program may
> be
> >> scanned conservatively.
> >
> > I have to think about this one. Which options are you thinking of?
>
> -findirect-dispatch
>
> With that option, everything except the stack is scanned precisely.
> However,
> there is some runtime overhead.
>
> Andrew.
Note that in the information you posted, the GC was scanning around 7.5MB of roots conservatively. It might be worth checking what those regions are.
The number of black-listed pages seems really high to me. Is the collector configured for too small a heap?
What's the platform?
Hans
next prev parent reply other threads:[~2011-04-02 0:27 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 [this message]
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
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=238A96A773B3934685A7269CC8A8D04272EFEFD5C3@GVW0436EXB.americas.hpqcorp.net \
--to=hans.boehm@hp.com \
--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).