Patches item #568226, was opened at 2002-06-12 16:01
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=303152&aid=568226&group_id=3152
Category: modules
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Matthew Krenzer (krenzer)
Assigned to: Nobody/Anonymous (nobody)
Summary: lock mutex in cleanup_interp_data
Initial Comment:
Under high loads I'd get seg faults at the following place:
(gdb) bt
#0 OneWordFind (tablePtr=0xfeef6144, key=0xdb6fa0 "")
at ./../generic/tclHash.c:567
#1 0xfeee1d04 in cleanup_interp_data
(clientData=0x44cf38, interp=0xdb6fa0)
at ns_xml.c:291
#2 0x7eb5c in DeleteInterpProc (interp=0xdb6fa0)
at ./../generic/tclBasic.c:1013
etc.
(There are actually two different entrance points for
cleanup_interp_data due to how the callbacks are
arranged and it seems as though it usually gets called
twice . . . I don't know why).
Anyway, from what I could tell of the problem it looked
like a thread concurrency issue on interp_hash and the
following patch seems to have fixed the problem..
----------------------------------------------------------------------
>Comment By: Matthew Krenzer (krenzer)
Date: 2002-10-08 12:22
Message:
Logged In: YES
user_id=562183
Was this patch going to be applied? Is there a problem with
it or did it just get forgotten?
I promise that the crash really can happen. :-)
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=303152&aid=568226&group_id=3152
