[Mono-bugs] [Bug 545034] MonoVS is extremely slow when the VM is set to use VMware's NAT network interface

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Sun Oct 18 19:13:37 EDT 2009


http://bugzilla.novell.com/show_bug.cgi?id=545034

User emp.007 at gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=545034#c6





--- Comment #6 from Evgeny Potashnik <emp.007 at gmail.com>  2009-10-18 17:13:29 MDT ---
Same problem in 0.6.4168 and one additional problem: when running remotely (not
debugging) visual studio completely freezes while the program runs. When it
terminates VS comes up with an exception dialog:

Mono.VisualStudio.Remoting.ConnectionClosedException: Connection closed.

Server stack trace: 
   at Mono.VisualStudio.Remoting.MultiplexedStream.CheckStatus()
   at Mono.VisualStudio.Remoting.MultiplexedStream.Read(Byte[] buffer, Int32
offset, Int32 count)
   at System.IO.BufferedStream.Read(Byte[] array, Int32 offset, Int32 count)
   at Mono.VisualStudio.Remoting.TcpMessageIO.StreamRead(Stream networkStream,
Byte[] buffer, Int32 count)
   at Mono.VisualStudio.Remoting.TcpMessageIO.ReceiveMessageStatus(Stream
networkStream, Byte[] buffer)
   at Mono.VisualStudio.Remoting.TcpPipeClientSink.ProcessMessage(IMessage msg,
ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders&
responseHeaders, Stream& responseStream)
   at
System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage
msg)

Exception rethrown at [0]: 
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage
reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData&
msgData, Int32 type)
   at Mono.VisualStudio.Mdb.IMdbManager.RunSession(DebuggingSession session)
   at Novell.MonoVS.RunRemotelyRunner.Run()
   at Novell.MonoVS.Package.RunRemotelyCallback(Object sender, EventArgs e)

-- 
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the mono-bugs mailing list