Bug 4339 - Crash when opening Designer
Summary: Crash when opening Designer
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Android Designer ()
Version: 2.9.x
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Lluis Sanchez
URL:
Depends on:
Blocks:
 
Reported: 2012-04-09 03:54 UTC by bvsimmons1204
Modified: 2012-06-01 08:35 UTC (History)
0 users

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description bvsimmons1204 2012-04-09 03:54:34 UTC
After installing the beta designer p2 I created a test android application and when I double clicked to open the design MonoDevelop crashed with the following details (you will also get this report directly as I enabled sending reports automatically)

System.ObjectDisposedException: Cannot access a disposed object.

Object name: 'System.Net.Sockets.Socket'.

   at System.Net.Sockets.Socket.EndAccept(IAsyncResult asyncResult)

   at System.Net.Sockets.TcpListener.EndAcceptTcpClient(IAsyncResult asyncResult)

   at Xamarin.AndroidDesigner.JavaProcessConnection.OnConnected(IAsyncResult res)

   at System.Net.LazyAsyncResult.Complete(IntPtr userToken)

   at System.Net.ContextAwareResult.CompleteCallback(Object state)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

   at System.Net.ContextAwareResult.Complete(IntPtr userToken)

   at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr userToken)

   at System.Net.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* nativeOverlapped)

   at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)
Comment 1 Lluis Sanchez 2012-06-01 08:35:04 UTC
I could not reproduce this exact error, but I think it is fixed. If you see it again with the most recent monodevelop version, please reopen.