Bug 2667 - MD locks up when Unable to communicate with Xcode exception is caught
Summary: MD locks up when Unable to communicate with Xcode exception is caught
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: unspecified
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Alan McGovern
Depends on:
Reported: 2011-12-28 12:41 UTC by Jackson Harper
Modified: 2013-04-02 14:33 UTC (History)
2 users (show)

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

Screenshot of stack (83.15 KB, image/png)
2011-12-28 12:41 UTC, Jackson Harper
Screenshot of stack with some line numbers (56.60 KB, image/png)
2011-12-28 12:42 UTC, Jackson Harper

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:

Description Jackson Harper 2011-12-28 12:41:41 UTC
Created attachment 1102 [details]
Screenshot of stack

Not exactly sure how to reproduce the exception, it seems to happen randomly while editing.

The real issue is it causes MD to completely lock up and eventually it crashes (once it brought down OSX with it).

Attached are a couple screenshots of the exception, unfortunately I can't C&P the stack trace.
Comment 1 Jackson Harper 2011-12-28 12:42:11 UTC
Created attachment 1103 [details]
Screenshot of stack with some line numbers
Comment 2 Mikayla Hutchinson [MSFT] 2011-12-28 14:40:16 UTC
We need to time out on the AppleScript driving Xcode, maybe we need to send the events directly for that though.
Comment 3 Alan McGovern 2011-12-29 09:21:24 UTC
The applescript does time out after approximately 30 seconds. I'm unsure if that timeout can be easily altered. I'd need to look up the applescript docs. Sending events directly to xcode may be the best option for this.
Comment 4 Alan McGovern 2011-12-29 09:26:10 UTC
The null ref is due to NSWorkspace.SharedWorkspace.LaunchedApplications returning null. I'm not sure what would cause this (i don't know the code). We can either work around this by never returning null or by using a different way (such as applescript) to check if xcode is running
Comment 5 Jeffrey Stedfast 2013-04-02 14:33:01 UTC
this has been fixed