[Mono-bugs] [Bug 50049][Maj] New - MonoThread domain-specific handling broken

[bugzilla-daemon@bugzilla.ximian.com]

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=50049

--- shadow/50049	2003-10-23 11:10:23.000000000 -0400
+++ shadow/50049.tmp.22872	2003-10-23 11:10:23.000000000 -0400
@@ -0,0 +1,25 @@
+Bug#: 50049
+Product: Mono/Runtime
+Version: unspecified
+OS: other
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Major
+Component: misc
+AssignedTo: dick@ximian.com                            
+ReportedBy: lupus@ximian.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: MonoThread domain-specific handling broken
+
+MonoThread is the unmanaged representation for the Thread object.
+The runtime should make sure the current MonoThread corresponds to the
+current domain, both in the finalizer thread and when appdomain changes
+happen. Currently, at least for the finalizer thread, the MonoThread object
+is not set, causing nullref exceptions when executing finalizers. If the
+object is not set correctly on domain changes it will cause random
+hard-to-track bugs, hence this is a major bug.