[Mono-bugs] [Bug 78083][Maj] New - nunit-gui: crash in native code when running nunit.mocks.tests.dll tests

[bugzilla-daemon at 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 matt at use.net.

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

--- shadow/78083	2006-04-11 22:12:57.000000000 -0400
+++ shadow/78083.tmp.6116	2006-04-11 22:12:57.000000000 -0400
@@ -0,0 +1,55 @@
+Bug#: 78083
+Product: Mono: Runtime
+Version: 1.1
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Major
+Component: GC
+AssignedTo: lupus at ximian.com                            
+ReportedBy: matt at use.net               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: nunit-gui: crash in native code when running nunit.mocks.tests.dll tests
+
+Please fill in this template when reporting a bug, unless you know what you
+are doing.
+Description of Problem:
+
+
+Steps to reproduce the problem:
+1. start nunit-gui.exe (2.2.7)
+2. file->open, select nunit.mocks.tests.dll
+3. click Run
+
+Actual Results:
+crash in native code. the problem appears to be tracable to this valgrind
+output:
+==6242== Thread 8:
+==6242== Invalid read of size 4
+==6242==    at 0x45BD2A: ves_icall_InternalInvoke (icall.c:2641)
+==6242==    by 0xF1FCDF0: ???
+==6242==    by 0xF1FC922: ???
+==6242==    by 0xE05CCD2: ???
+==6242==  Address 0x6310394 is 116 bytes inside a block of size 128 free'd
+==6242==    at 0x4A190DA: free (vg_replace_malloc.c:222)
+==6242==    by 0x48EAA7: mono_domain_free (domain.c:977)
+==6242==    by 0x4817AA: unload_thread_main (appdomain.c:1308)
+==6242==    by 0x4B5633: thread_start_routine (threads.c:194)
+==6242==    by 0x4CA0C6: GC_start_routine (pthread_support.c:1330)
+==6242==    by 0x50CEBB8: pthread_start_thread (manager.c:310)
+
+There are many others errors after this, all relating to memory being
+read/written after being free'd by mono_domain_free().
+
+Expected Results:
+shouldn't crash.
+
+How often does this happen? 
+
+
+Additional Information: