Bug 37542 - Xamarin Studio ALWAYS becomes unresponsive on restart
Summary: Xamarin Studio ALWAYS becomes unresponsive on restart
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 5.10 (C6SR3)
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: master
Assignee: Bugzilla
Depends on:
Reported: 2016-01-09 11:11 UTC by George Edwards
Modified: 2017-07-20 18:38 UTC (History)
2 users (show)

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:

Description George Edwards 2016-01-09 11:11:14 UTC
When I shut down my iMac, I usually leave the option to relaunch closed problems next time I turn on my device. Every time I do this, when I come to use Xamarin, it is responsive and requires a "ctrl + click" and "Force Quit" then a restart and it works fine. It has done this for weeks and I always report the issue to Apple through the automated pop up however, nothing has ben done. 

I am using an iMac (21.5-inch, Mid 2014)

  System Version:	OS X 10.11.2 (15C50)
  Kernel Version:	Darwin 15.2.0
  Boot Volume:	Macintosh HD
Comment 1 Amy Burns 2017-07-20 18:38:51 UTC
Thanks so much for taking the time to submit this report! I apologies for the length of time it has taken to respond to your bug. I'm currently trying to go through and triage outstanding bugs for our engineers.

I attempted to reproduce this issue based on the bug description with the latest Visual Studio 2017 for Mac Preview version 7.1, and I was unable to hit the problem. 

If this issue is still occurring for you, please reopen this report and attach a reproduction, ideally starting with a new template project and then adding just the code necessary to demonstrate the issue.