Bug 42449 - VS crashes when MAC agent loses connection
Summary: VS crashes when MAC agent loses connection
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: General ()
Version: 4.1.0 (C7)
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-07-09 06:05 UTC by Farhad Adeli
Modified: 2016-12-22 19:43 UTC (History)
7 users (show)

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

vs crash screen shot (19.71 KB, image/png)
2016-07-09 06:05 UTC, Farhad Adeli

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 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 Farhad Adeli 2016-07-09 06:05:55 UTC
Created attachment 16621 [details]
vs crash screen shot

When VS is connected to the MAC agent and MAC agent suddenly becomes inaccessible (goes to sleep, restarts) VS crashes and sometimes the whole windows becomes unresponsive.

Xamarin (34a92cd)
Xamarin.Android (7db2aac)
Xamarin.iOS (3cf8aae)

Problem signature:
  Problem Event Name:	CLR20r3
  Problem Signature 01:	devenv.exe
  Problem Signature 02:	14.0.25123.0
  Problem Signature 03:	56f22f32
  Problem Signature 04:	Renci.SshNet
  Problem Signature 05:	2014.4.6.0
  Problem Signature 06:	547083b0
  Problem Signature 07:	99e
  Problem Signature 08:	29
  Problem Signature 09:	System.NullReferenceException
  OS Version:	6.3.9600.
  Locale ID:	1033
  Additional Information 1:	5861
  Additional Information 2:	5861822e1919d7c014bbb064c64908b2
  Additional Information 3:	84a0
  Additional Information 4:	84a09ea102a12ee665c500221db8c9d6
Comment 1 Farhad Adeli 2016-07-09 07:21:46 UTC
Microsoft Visual Studio Enterprise 2015
Version 14.0.25123.00 Update 2
Microsoft .NET Framework
Version 4.6.01055

My Enviroment:
VS running on PC Win8.1 with AMD CPU, started new project from templates.
MAC running on VMware Workstation 12 on laptop with Win8.1 and Corei5 CPU, xCode 7.3.1, xamarin.ios-, xamarin.mac-, XamarinStudio-
PC is directly connected to laptop with LAN cable
VM network is running in bridged mod.

VS crashes when MAC is suspended or shuts down.
Comment 2 Ashley Gazich [MSFT] 2016-07-14 21:55:27 UTC
Hi Farhad, thanks for reaching out. If I am understanding things correctly, this is an unsupported configuration. Apple’s licensing terms require a physical Mac for iOS development. As such, I am closing this report.
Comment 3 Farhad Adeli 2016-07-15 05:44:56 UTC
It does not matter where my MAC is, and i am not reporting a bug for MAC. this is as the problem show is a un-handled  exception with Renci.SshNet library and has nothing to do with mac or my configuration. if you dont wana fix a bug just say it, don't make excuses ...
If you like just edit my comment about mac running on vm and we are good to go.
Comment 4 Brendan Zagaeski (Xamarin Team, assistant) 2016-07-20 20:41:38 UTC
This is quite possibly a duplicate of Bug 41918.  If the original reporter concurs with that assessment he may mark it as a duplicate himself.

If the original reporter would instead be looking for additional investigation on this issue as a separate bug, the Xamarin team would (as a first step) be looking to get the complete stack trace of the NullReferenceException (from Event Viewer) in an environment where the Windows machine is connected to a physical Mac or a Mac OS running virtualized on a physical Mac to comply with Apple's terms of use.  Thanks in advance.
Comment 5 Adrian Alonso 2016-12-22 19:43:00 UTC
This issue should be already fixed in the latest release.