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=77075 --- shadow/77075 2007-01-01 17:52:43.000000000 -0500 +++ shadow/77075.tmp.26920 2007-01-01 17:56:40.000000000 -0500 @@ -83,6 +83,31 @@ ------- Additional Comments From [EMAIL PROTECTED] 2006-03-30 08:03 ------- *** Bug 77779 has been marked as a duplicate of this bug. *** ------- Additional Comments From [EMAIL PROTECTED] 2006-09-10 14:30 ------- *** Bug 79349 has been marked as a duplicate of this bug. *** + +------- Additional Comments From [EMAIL PROTECTED] 2007-01-01 17:56 ------- +There is some information about this bug on the Boehm mailing list +archives: + +http://comments.gmane.org/gmane.comp.programming.garbage-collection.boehmgc/1202 + +The solution seems that someone found was: + +"First, after a few seconds of thread creation and destruction i always +run into an error that GC_stop_world calls SuspendThread on an invalid +handle. The windows GetLastError() code is 6. This happens with 6.6 +and 6.7 and is very repeatable for me. First i tried to catch this +situation and simply close the handle in the thread table when such a +situation came up but this did not help very much. + +Also the comment above in the function told me that i'm not the +first one who had this problem. + +So i solved it by using GC_CreateThread and linking to a static +compiled library instead of using the DLL magic. I never had invalid +handles anymore." + +I do not know what the "dll magic" is that they are talking about on +that thread. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
