[Mono-bugs] [Bug 81369][Nor] New - Async Network Application crashes eventually

[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 stefan at neokast.com.

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

--- shadow/81369	2007-04-13 08:02:41.000000000 -0400
+++ shadow/81369.tmp.27877	2007-04-13 08:02:41.000000000 -0400
@@ -0,0 +1,110 @@
+Bug#: 81369
+Product: Mono: Class Libraries
+Version: 1.2
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: System
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: stefan at neokast.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Async Network Application crashes eventually
+
+Please fill in this template when reporting a bug, unless you know what you
+are doing.
+Description of Problem:
+
+Mono application crashes likely on Net I/O operation. The application is
+network intense with many TCP/UDP connections to different hosts. All
+network I/O is async.
+
+Steps to reproduce the problem:
+1. It happens after the application runs for hours/days.
+2. 
+3. 
+
+Actual Results:
+
+
+Expected Results:
+
+
+How often does this happen? 
+
+It happens with an expected mean time of a 10-30 hours. It may be related
+to how many network I/O operations are performed. So basically there could
+be a very small chance it happens on some sort of socket operation (all async).
+
+Additional Information:
+
+RHEL 4.4 / CentOS 4.4
+
+Stacktrace:
+
+  at (wrapper managed-to-native)
+System.Object.__icall_wrapper_mono_delegate_begin_invoke (object,intptr)
+<0x00004>
+  at (wrapper managed-to-native)
+System.Object.__icall_wrapper_mono_delegate_begin_invoke (object,intptr)
+<0xffffffff>
+  at (wrapper delegate-begin-invoke)
+System.MulticastDelegate.begin_invoke_IAsyncResult_object_AsyncCallback_object
+(object,System.AsyncCallback,object) <0xffffffff>
+  at System.Threading.ThreadPool.QueueUserWorkItem
+(System.Threading.WaitCallback,object) <0x00015>
+  at SocketAsyncResult.CompleteAllOnDispose (System.Collections.Queue)
+<0x0009f>
+  at SocketAsyncResult.Complete () <0x00151>
+  at Worker.Send () <0x000c7>
+  at (wrapper delegate-invoke) System.MulticastDelegate.invoke_void ()
+<0xffffffff>
+  at (wrapper runtime-invoke) System.Object.runtime_invoke_void
+(object,intptr,intptr,intptr) <0xffffffff>
+
+Native stacktrace:
+
+        mono [0x815ebbd]
+        mono [0x8148af7]
+        [0x353440]
+        mono [0x812508a]
+        mono(mono_array_new_specific+0xae) [0x80ddf5e]
+        mono [0x80a2f19]
+        mono [0x80a2aa5]
+        mono [0x80a29c9]
+        mono [0x80a99fb]
+        [0x995d45]
+        [0x995cef]
+        [0x995c86]
+        [0x1e4ed98]
+        [0x9daa3a]
+        [0x9da878]
+        [0x9da788]
+        [0xed63c9]
+        mono [0x81489a0]
+        mono(mono_runtime_invoke+0x27) [0x80dbde7]
+        mono(mono_runtime_invoke_array+0x268) [0x80dd368]
+        mono [0x80df431]
+        mono [0x80a24bd]
+        mono [0x80a1043]
+        mono [0x8094d72]
+        mono [0x80fdfc7]
+        mono [0x811d705]
+        /lib/libpthread.so.0 [0x7bb3b6]
+        /lib/libc.so.6(__clone+0x5e) [0x70733e]
+
+Debug info from gdb:
+
+
+
+
+=================================================================
+Got a SIGSEGV while executing native code. This usually indicates
+a fatal error in the mono runtime or one of the native libraries
+used by your application.
+=================================================================