libgcj/222: GC: failure upon allocation inside a finalizer
Boehm, Hans
hans_boehm@hp.com
Mon May 8 16:16:00 GMT 2000
The following reply was made to PR libgcj/222; it has been noted by GNATS.
From: "Boehm, Hans" <hans_boehm@hp.com>
To: "'Tom Tromey'" <tromey@cygnus.com>, "Boehm, Hans" <hans_boehm@hp.com>
Cc: "'java-gnats@sourceware.cygnus.com'"
<java-gnats@sourceware.cygnus.com>,
"'bryce@albatross.co.nz'"
<bryce@albatross.co.nz>, green@cygnus.com
Subject: RE: libgcj/222: GC: failure upon allocation inside a finalizer
Date: Mon, 8 May 2000 15:59:33 -0700
One minor complication is that in the single-threaded case, everything will
presumably have to continue working as it does now.
The alternative would be to require an explicit client call to run
finalizers. That's probably closer to correct, but I suspect it would break
a lot more existing code. Single-threaded finalization just doesn't work
well.
Hans
-----Original Message-----
From: Tom Tromey [ mailto:tromey@cygnus.com ]
Sent: Monday, May 08, 2000 3:31 PM
To: Boehm, Hans
Cc: 'java-gnats@sourceware.cygnus.com'; 'bryce@albatross.co.nz';
tromey@cygnus.com; green@cygnus.com
Subject: RE: libgcj/222: GC: failure upon allocation inside a finalizer
Hans> We probably need to add some mechanism for having the collector
Hans> notify the finalizer thread when there is something to do.
Hans> Perhaps a callback that is invoked at the end of a GC when there
Hans> are objects to be finalized?
That would be perfect. We'll have the finalizer thread wait on a
condition variable, and we'll have the callback notify it.
Tom
More information about the Java-prs
mailing list