This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: [PATCH]: natThread.cc: Destroy join sync objects in finalizer
- From: Tom Tromey <tromey at redhat dot com>
- To: "Boehm, Hans" <hans dot boehm at hp dot com>
- Cc: "'Bryce McKinlay'" <mckinlay at redhat dot com>,gnustuff at thisiscool dot com, GCJ Patches <java-patches at gcc dot gnu dot org>
- Date: 12 Sep 2004 18:00:55 -0600
- Subject: Re: [PATCH]: natThread.cc: Destroy join sync objects in finalizer
- References: <B27561804CF1BE4F8943BB2CB29E18EA062D08@hplextmp.hpl.hp.com>
- Reply-to: tromey at redhat dot com
Hans> It's probably better if we don't leak resources in that case,
Hans> but I'm not sure it qualifies as a libgcj bug if we do.
Good point -- I had conflated all the failure modes in my mind, but in
fact as long as we avoid potentially VM-crashing bugs, we're ok.
Resource leaks due to bad user code are unavoidable; after all a
malicious applet could just new Object() in a loop.
Tom