[Mono-bugs] [Bug 80664][Maj] New - mono_marshal_get_runtime_invoke causes deadlock

[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 bmaurer at users.sf.net.

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

--- shadow/80664	2007-01-29 19:06:51.000000000 -0500
+++ shadow/80664.tmp.20635	2007-01-29 19:06:51.000000000 -0500
@@ -0,0 +1,28 @@
+Bug#: 80664
+Product: Mono: Runtime
+Version: 1.2
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Major
+Component: misc
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: bmaurer at users.sf.net               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: mono_marshal_get_runtime_invoke causes deadlock
+
+The method mono_marshal_get_runtime_invoke acquires locks in an
+inconsistent order. First, it acquires the marshal lock, then calls
+signature_dup_add_this which calls mono_ptr_class_get and acquires the
+loader lock. after all of these are released, it then acquires the loader
+lock, then the marshal lock.
+
+I believe this is the cause of a deadlock I'm encountering on XSP. I can
+reproduce this deadlock on a 4 core machine with:
+
+ab -c20 -n10000 http://HOST:8080/1.1/handlers/empty.ashx