public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "chris dot pickett at mail dot mcgill dot ca" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug AWT/16203] New: need to kill awt helper threads on gui app exit Date: Fri, 25 Jun 2004 18:40:00 -0000 [thread overview] Message-ID: <20040625183754.16203.chris.pickett@mail.mcgill.ca> (raw) Sun gives three conditions that lets awt terminate its helper threads, as of 1.4, namely that: 1) There are no displayable AWT or Swing components. 2) There are no native events in the native event queue. 3) There are no AWT events in java EventQueues. http://java.sun.com/j2se/1.4.2/docs/api/java/awt/doc-files/AWTThreadIssues.html It seems like it would be a good idea to get something like that into Classpath. Sun's 1.4.2 VM has it's own "Suspend Checker Thread" (visible in "ctrl-\"-generated thread/stack dumps) which appears to be some kind of reaper. The test case attached below hangs on SableVM, which uses a recent Classpath. Apparently it does not hang on gij, but that may be for another reason. -- Summary: need to kill awt helper threads on gui app exit Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P2 Component: AWT AssignedTo: fitzsim at redhat dot com ReportedBy: chris dot pickett at mail dot mcgill dot ca CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16203
next reply other threads:[~2004-06-25 18:37 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-06-25 18:40 chris dot pickett at mail dot mcgill dot ca [this message] 2004-06-25 18:42 ` [Bug AWT/16203] " chris dot pickett at mail dot mcgill dot ca 2004-06-26 0:09 ` pinskia at gcc dot gnu dot org 2004-06-27 21:41 ` fitzsim at redhat dot com 2005-01-04 20:20 ` fitzsim at redhat dot com 2005-01-12 14:04 ` chris dot pickett at mail dot mcgill dot ca 2005-04-20 1:59 ` pinskia at gcc dot gnu dot org 2005-09-14 13:52 ` [Bug awt/16203] " fitzsim at redhat dot com 2005-09-14 13:54 ` fitzsim 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=20040625183754.16203.chris.pickett@mail.mcgill.ca \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).