[Mono-bugs] [Bug 65414][Nor] Changed - [PATCH] Thread Local Data Slots do not survive nested appdomain transitions
Tue, 7 Sep 2004 12:51:35 -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 firstname.lastname@example.org.
--- shadow/65414 2004-09-07 12:44:04.000000000 -0400
+++ shadow/65414.tmp.1597 2004-09-07 12:51:35.000000000 -0400
@@ -114,6 +114,13 @@
you'd know: it causes additional overhead at thread creation and
destruction and it uses more memory than sticking the per-thread data
in the per-thread object that is already readily available.
Making LocalDataStoreSlot hold an integer and use that to index an
array instead of using an hash table is perfectly fine, but unrelated
to the rest of the discussion.
+------- Additional Comments From email@example.com 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