[Mono-bugs] [Bug 62207][Cri] New - Remoting Memory Leak

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Fri, 30 Jul 2004 17:53:49 -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 rlyon@novell.com.

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

--- shadow/62207	2004-07-30 17:53:49.000000000 -0400
+++ shadow/62207.tmp.28664	2004-07-30 17:53:49.000000000 -0400
@@ -0,0 +1,48 @@
+Bug#: 62207
+Product: Mono: Class Libraries
+Version: unspecified
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Critical
+Component: CORLIB
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: rlyon@novell.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Remoting Memory Leak
+
+Please fill in this template when reporting a bug, unless you know what 
+you are doing. 
+Description of Problem: 
+ 
+When we run iFolder on Mono for extended periods of time we run out of 
+memory and experience strange behavior.  We have isolated the memory leak 
+to the remoting code. I have created an over-the-top example, which will 
+cause the machine to run out of memory very quickly (under 5 minutes). 
+ 
+Steps to reproduce the problem: 
+1. In one shell, run "mono RemotingServer.exe". 
+2. In another shell on the same machine, run "mono RemotingClient.exe". 
+ 
+Actual Results: 
+ 
+In less than five minutes the remoting server will stop responding.  Also, 
+an OutOfMemoryException is not thrown. 
+ 
+Expected Results: 
+ 
+This code should theorically be able to run forever.  This code performs 
+as expected on .Net/Windows. 
+ 
+How often does this happen?  
+ 
+Always. 
+ 
+Additional Information: 
+ 
+In our iFolder application, we see this problem after three to four hours.