public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "aph at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug libgcj/30886] Memory collection deadlock Date: Thu, 22 Feb 2007 15:19:00 -0000 [thread overview] Message-ID: <20070222151914.7028.qmail@sourceware.org> (raw) In-Reply-To: <bug-30886-11288@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from aph at gcc dot gnu dot org 2007-02-22 15:19 ------- I can't see anything in the Java Language Standard that suggests that your test case must terminate. Garbage collection is not deterministic, and may not collect all objects. When I tried your test case one object was not reclaimed, probably because a reference to it still existed in the stack. In gcj we do a conservative scan of the stack, and there may be stale references that prevent objects from being collected. To guarantee that everything is collected you have to do a precise scan, and we deliberately don't do that. -- aph at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution| |INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30886
next prev parent reply other threads:[~2007-02-22 15:19 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-02-20 15:47 [Bug java/30886] New: " swagiaal at redhat dot com 2007-02-20 15:48 ` [Bug java/30886] " swagiaal at redhat dot com 2007-02-21 13:38 ` [Bug libgcj/30886] " aph at gcc dot gnu dot org 2007-02-22 15:11 ` swagiaal at redhat dot com 2007-02-22 15:19 ` aph at gcc dot gnu dot org [this message] 2007-02-22 15:35 ` swagiaal at redhat dot com
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=20070222151914.7028.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=java-prs@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: linkBe 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).