Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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 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.
this bug report is similar to bug 42449, however, this time I am connected to a physical mac, not a VM.
short problem description:
If the iOS designer in VS is open and the connection to the mac is suddenly lost (mac goes to sleep, or whatever), visual studio crashes. If the designer view IS NOT open, then no issues.
steps to reproduce:
1. open a xamarin iOS prject, and connect to a physical mac
2. open a storyboard file and make sure it loads correctly.
3. puts the mac to sleep or just turn the mac's wifi off
4. visual studio will/should crash
visual studio crashes when the designer view is open and the connection to the mac is suddenly lost
visual studio should not crash, instead display a message in the designer view that the designer is not available and attempt to connect back to the mac as soon as the connection is restored.
Can you attach the log files from the session which crashed? We'll need that information to figure out the root cause of the problem. There should be an option in the 'Help' menu to zip up the logs for the last week.
Created attachment 16992 [details]
last 7 days of logs
I believe the crash happened on the 4th of Aug.
The logs from the 4th of August don't have any error information. I did scan all the other logs and nothing specific to the designer is showing up, but there are some non-designer related issues which could be contributing to the issue.
Would you be able to trigger the problem again and then zip up a fresh set of logs? That would ensure I'm looking at the right thing then. It would also help me cross reference a 'known crasher' log with the other logs you've sent to see if there are similarities.
Thanks for looking at the logs.
If this issue happens with newer releases then please attach the logs and we will investigate further. Thanks!