[Mono-bugs] [Bug 77075][Maj] Changed - "SuspendThread failed!" on windows

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Wed May 2 12:59:18 EDT 2007

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 joncham at gmail.com.


--- shadow/77075	2007-02-01 08:22:54.000000000 -0500
+++ shadow/77075.tmp.17215	2007-05-02 12:59:18.000000000 -0400
@@ -313,6 +313,22 @@
 and the post from the boehm-gc-list seemed conclusive.
 The patch helped to find out that there is probably no
 race in GC_new_thread () as implied by the missing locks
 that can't be used inside DllMain ().
+------- Additional Comments From joncham at gmail.com  2007-05-02 12:59 -------
+80798 may be a duplicate of this. I have a small sample in C++ that
+reproduces the error without mono. Basically, it seems that
+GetExitCodeThread indicates a thread is still active (STILL_ACTIVE).
+However, the thread is in the process of exiting; the last pieces of
+user code have been executed and it has returned from the thread proc.
+The call to SuspendThread then fails with an 'Access denied' error.
+I submitted an approved proposal for 80798. I will checkin that
+proposal in a few days unless there is any new concern.
+I tried to reproduce the test case with xsp from svn, but I could not
+get it to work (xsp launched but browser never connected). If someone
+can reproduce problem with svn, and then try with modification
+proposed in bug 80798, that would be good.

More information about the mono-bugs mailing list