public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "Hans dot Boehm at hp dot com" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug libgcj/16662] IllegalMonitorStateException in EventQueue.getNextEvent(): possible hash synchronization bug? Date: Tue, 10 Aug 2004 00:44:00 -0000 [thread overview] Message-ID: <20040810004434.27903.qmail@sourceware.org> (raw) In-Reply-To: <20040721214713.16662.mckinlay@redhat.com> ------- Additional Comments From Hans dot Boehm at hp dot com 2004-08-10 00:44 ------- One other small piece of data: In the failing runs I've seen, only a single heavy lock (for the user lock which eventually causes the problem) is allocated at the beginning of the run. Thus the chain of heavy locks is indeed completely static, as should be expected. I'm attempting to reproduce the failure with some circular buffer logging code, but even without that, it currently takes me hours to reproduce the problem. Based on further inspection, there does seem to be another problem with Object.wait() only notifying a single thread if it inflates the lock. It should notify all waiters. But that seems to be an extremely unlikely scenario, and should only result in performance or possibly deadlock issues, and only if there are more than two threads involved. I will include it in the patch I'm accumulating. Hans -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16662
next prev parent reply other threads:[~2004-08-10 0:44 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-07-21 21:47 [Bug libgcj/16662] New: " mckinlay at redhat dot com 2004-07-26 18:57 ` [Bug libgcj/16662] " mckinlay at redhat dot com 2004-08-05 0:56 ` Hans dot Boehm at hp dot com 2004-08-07 0:43 ` Hans dot Boehm at hp dot com 2004-08-10 0:44 ` Hans dot Boehm at hp dot com [this message] 2004-08-10 18:02 ` mckinlay at redhat dot com 2004-08-10 18:30 ` Hans dot Boehm at hp dot com 2004-08-12 17:56 ` cvs-commit at gcc dot gnu dot org 2004-08-12 18:38 ` pinskia at gcc dot gnu dot org 2004-09-07 21:15 ` cvs-commit at gcc dot gnu dot org 2004-10-06 22:47 ` cvs-commit at gcc dot gnu dot org 2004-12-01 0:32 ` cvs-commit at gcc dot gnu dot org [not found] <bug-16662-6651@http.gcc.gnu.org/bugzilla/> 2007-05-15 9:46 ` rob1weld at aol 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=20040810004434.27903.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).