[Mono-bugs] [Bug 62207][Cri] Changed - Remoting Memory Leak
bugzilla-daemon@bugzilla.ximian.com
bugzilla-daemon@bugzilla.ximian.com
Mon, 2 Aug 2004 20:16:40 -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 bmaurer@users.sf.net.
http://bugzilla.ximian.com/show_bug.cgi?id=62207
--- shadow/62207 2004-08-02 18:13:49.000000000 -0400
+++ shadow/62207.tmp.593 2004-08-02 20:16:40.000000000 -0400
@@ -1,12 +1,12 @@
Bug#: 62207
Product: Mono: Class Libraries
Version: unspecified
OS: unknown
OS Details:
-Status: NEW
+Status: NEEDINFO
Resolution:
Severity: Unknown
Priority: Critical
Component: CORLIB
AssignedTo: mono-bugs@ximian.com
ReportedBy: rlyon@novell.com
@@ -58,6 +58,30 @@
leaving for holidays.
------- Additional Comments From miguel@ximian.com 2004-08-02 18:13 -------
Please do not set bugs to hidden, it does not work for Mono anyways.
+
+------- Additional Comments From bmaurer@users.sf.net 2004-08-02 20:16 -------
+Miguel and I were unable to repro this. When the client runs, it displays
+
+Unhandled Exception: System.Net.WebException: Error: ConnectFailure
+in <0x000cb> System.Net.HttpWebRequest:EndGetRequestStream
+(System.IAsyncResult)
+in <0x000bc> System.Net.HttpWebRequest:GetRequestStream ()
+in <0x00348>
+System.Runtime.Remoting.Channels.Http.HttpClientTransportSink:CreateWebRequest
+(string,System.Runtime.Remoting.Channels.ITransportHeaders,System.IO.Stream)
+in <0x00113>
+System.Runtime.Remoting.Channels.Http.HttpClientTransportSink:ProcessMessage
+(System.Runtime.Remoting.Messaging.IMessage,System.Runtime.Remoting.Channels.ITransportHeaders,System.IO.Stream,System.Runtime.Remoting.Channels.ITransportHeaders&,System.IO.Stream&)
+in <0x0006d>
+System.Runtime.Remoting.Channels.SoapClientFormatterSink:SyncProcessMessage
+(System.Runtime.Remoting.Messaging.IMessage)
+in <0x0031b> System.Runtime.Remoting.Proxies.RemotingProxy:Invoke
+(System.Runtime.Remoting.Messaging.IMessage)
+in <0x0037f> System.Runtime.Remoting.Proxies.RealProxy:PrivateInvoke
+(System.Runtime.Remoting.Proxies.RealProxy,System.Runtime.Remoting.Messaging.IMessage,System.Exception&,object[]&)
+
+
+It seems that it never connects to the server.