[Mono-bugs] [Bug 27663][Maj] Changed - Assemblies are never unloaded when an appdomain is unloaded

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Tue Apr 4 10:03:52 EDT 2006


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

http://bugzilla.ximian.com/show_bug.cgi?id=27663

--- shadow/27663	2006-02-01 11:30:53.000000000 -0500
+++ shadow/27663.tmp.14742	2006-04-04 10:03:52.000000000 -0400
@@ -158,6 +158,18 @@
 
 ------- Additional Comments From vargaz at gmail.com  2005-07-23 07:23 -------
 *** Bug 75613 has been marked as a duplicate of this bug. ***
 
 ------- Additional Comments From vargaz at gmail.com  2006-02-01 11:30 -------
 *** Bug 77436 has been marked as a duplicate of this bug. ***
+
+------- Additional Comments From vargaz at gmail.com  2006-04-04 10:03 -------
+Assembly unloading should work now in HEAD (Unless the patch has to
+be reverted). The testcase will not work tough, because when calling
+CreateInstanceFromAndUnwrap, the remoting code will load the assembly
+into the _current_ appdomain, not the child, so it will not be 
+unloaded when the child appdomain is unloaded. A workaround is to 
+avoid remoting calls to types in the assemblies which should be
+unloaded, i.e. create a proxy class which will be called by remoting, 
+and have the proxy class load the assembly and interact with it 
+entirely in the child appdomain.
+


More information about the mono-bugs mailing list