On Mon, 19 Jun 2000, Dr Wes Munsil wrote:
> This one appears to be different. Vignette StoryServer 5.0, Tcl 8.2.3,
> TclBlend 1.2.5, JDK 1.1.8, SunOS 5.6. TclBlend patched as described in
> my last post. Little flexibility to upgrade to more recent versions of
> anything.
>
> Every thread stacktrace that seems relevant is below. The
> java_lang_UNIXProcess_run is presumably my call of Runtime.exec ("env").
> No idea why it is in sysMonitorWait. May or may not be related to the
> deadlock.
>
> Thoughts, opinions, wild guesses encouraged.
I think this one is along the same lines. The finalizer thread seems
to be called decrRefCount() which is calling FreeTclObject(). I
think we need a more general solution to the problem of the
finalizer thread walking into an interp at some random time.
Can we create a queue of objects that have been finalized?
We could then clear this queue in a Tcl "after idle" call.
Should be make the gc thread block until a given Tcl event
has finished? This would need to be done by adding an event
to the Tcl event queue and then letting the GC thread go
when Tcl was ready to process the event.
What do folks think of these approaches?
Mo DeJong
Red Hat Inc
----------------------------------------------------------------
The TclJava mailing list is sponsored by Scriptics Corporation.
To subscribe: send mail to [EMAIL PROTECTED]
with the word SUBSCRIBE as the subject.
To unsubscribe: send mail to [EMAIL PROTECTED]
with the word UNSUBSCRIBE as the subject.
To send to the list, send email to '[EMAIL PROTECTED]'.
An archive is available at http://www.mail-archive.com/tcljava@scriptics.com
