Please do not reply to this email- if you want to comment on the bug, go to the URL shown below and enter your comments there.
Changed by [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=80602 --- shadow/80602 2007-03-02 16:40:15.000000000 -0500 +++ shadow/80602.tmp.17772 2007-03-02 16:43:50.000000000 -0500 @@ -92,6 +92,20 @@ ------- Additional Comments From [EMAIL PROTECTED] 2007-03-02 16:40 ------- Created an attachment (id=18815) Trace of the problem occuring + +------- Additional Comments From [EMAIL PROTECTED] 2007-03-02 16:43 ------- +Oops, the second attachment obviously does not have the warning and is +what happens when everything goes okay. + +This is a problem I reported to Phillip and I've still been working on +trying to find out why it happens. I found out some information +recently, though. + +It seems to be related to a race where pthread_key_delete is being +called before the thread has exited, which invalidates the key and +when the thread exits it can't call the destructor (hence why we get +the error where it tries PTHREAD_KEY_MAX times to deallocate the key +data). _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
