[Mono-bugs] [Bug 71274][Nor] Changed - finalizer-... tests randomly crash on x86 (Environment.Exit race)
bugzilla-daemon@bugzilla.ximian.com
bugzilla-daemon@bugzilla.ximian.com
Tue, 19 Apr 2005 11:22:08 -0400 (EDT)
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 lupus@ximian.com.
http://bugzilla.ximian.com/show_bug.cgi?id=71274
--- shadow/71274 2005-04-19 01:57:05.000000000 -0400
+++ shadow/71274.tmp.27581 2005-04-19 11:22:08.000000000 -0400
@@ -97,6 +97,29 @@
------- Additional Comments From gonzalo@ximian.com 2005-04-19 01:57 -------
I hit the problem in bug #72741 if i don't add a Sleep in the
threadstart method. Once the program asserts (takes a few tries), it
fails with just 3-10 threads afterwards. Removing the .wapi directory
makes it "work" better again.
+
+------- Additional Comments From lupus@ximian.com 2005-04-19 11:22 -------
+Zoltan, please commit the change. Also, readd a few gpointer fields
+to MonoThread to both the C# and C types for later use.
+We should later change the code that sets the thread state to use the
+interlocked API instead of the heavy weight monitor lock.
+
+Currently miguels test fails with:
+** ERROR **: file handles.c: line 659 (_wapi_replace_handle):
+assertion failed: (new_off != 0)
+aborting...
+Aborted
+
+The next runs will fail with:
+** ERROR **: file handles.c: line 371 (_wapi_handle_new): assertion
+failed: (offset != 0)
+aborting...
+Aborted
+
+After a few failing runs, any mono program will die with the same
+assert, which is really bad. Removing ~/.wapi fixes it.
+Also, this has nothing to do with the original bug report, though it
+needs to be fixed to expose the original issue.