[Mono-bugs] [Bug 65414][Nor] Changed - [PATCH] Thread Local Data Slots do not survive nested appdomain transitions

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Tue, 7 Sep 2004 14:19:18 -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.


--- shadow/65414	2004-09-07 12:51:35.000000000 -0400
+++ shadow/65414.tmp.3846	2004-09-07 14:19:18.000000000 -0400
@@ -121,6 +121,14 @@
 ------- Additional Comments From bmaurer@users.sf.net  2004-09-07 12:51 -------
 "Currently the thread object is shared" -- exactly, this is the 
 problem. [ThreadStatic] is not shared across appdomains, so it helps 
 with this situation. The value of stuff we put in TLS *MUST* not be 
 shared between appdomains, so putting it in the Thread object does 
 not work.
+------- Additional Comments From lupus@ximian.com  2004-09-07 14:19 -------
+Do you have an idea where the ThreadStatic values are stored?
+Apparently not: they are stored in a field pointed to by the Thread
+object. So it is no different having the hash as a direct field in
+MonoThread or having it as a field of a field which is what using
+ThreadStatic makes it become. If you see different behaviour there is
+some other bug or you didn't test properly.