I'm trying to use Visual Studios for Mac (Preview 9) to code apps in Xamarin but occasionally, not only does Xamarin freezes but it freezes all my other programs that I'm using on my Macbook Pro retina 15 inch mid 2015 model. The only solution to get my MacBook Pro to respond to me again is to hold down the power button till it shuts down and then restart my entire machine. I see that the Macbook Pro model that I'm using only contains 16GB of RAM. I normally open up an instance of Chrome to watch my Udemy video and have an instance of Visual Studios opened to code as I watch along. I also have an instance of the iPhone simulator opened as well. When my Macbook Pro freezes, I can open Activity Monitor to check out the memory usage for Visual Studios for Mac and at that point, the RAM used by Visual Studios is approximately 9-10GB, sometimes even higher.
Did you know you can report issues with Visual Studio 2017 or Visual Studio for Mac directly within the IDE? Just use Help > Report a Problem to file your issue. Bug 60190 - Xamarin Mac Agent losing connection or freezes during build when 'doesn't like' included resources.
Why does Visual Studios consume so much memory? I have a feeling that because it is hogging all the resources, it is causing my MacBook Pro to freeze / be unresponsive. As a counter-point to @Gusman comment, I also been using MD, XS, VS4M since each was introduced, and while there are rough areas (VS4M does have memory leaks, so restart the IDE every couple of hours), I actually have a better experience with XS/VS4M then using VS and certainly in areas of large projects, XS outperforms VS in so many ways (but VS4M is starting to becoming bloated like VS now that I disable 50%+ of the Addins), but it depends upon your hardware, your usage pattern, etc. – May 4 '17 at 21:35. @Gusman Agree to disagree w/ you on that. Intellisense is Roslyn-based across the board now so yellow apples to red apples comparison and personally I am not a big fan of Intellisense as I can code as well in vi as I can in XS/VS and wish there was a way to completely disable it via shortcut.
I routinely just use vi with XS/VS4M running in the background for the SDB. VS 2015 is ok, but 2017 routinely crashes on our large solutions and as a result is unusable for a large number of our projects and since it is still locked to 32bit, this will not change for the foreseeable future. – May 4 '17 at 21:55.
Yesterday I've installed bootcamp, Windows 10 Pro, on my new tb/MBP (late 2016). Everything worked fine until I've installed Visual Studio 2015 (Update 3) with all of its components (50GB).
After I've rebooted the computer, it took 10 minutes to load Windows (waiting at the dark screen with Windows logo and dots loading animation). Then - the keyboard and trackpad do not respond (even the keyboard light is turned off). The Touch Bar sometimes works and sometimes not. I've rebooted to macOS and everything works fine. I've read many threads and saw that it may be related to Hyper-V, which Visual Studio uses for Mobile Developement. So, how can I disable Hyper-V so I can get back my MBP to normal? I don't want to re-install Windows, and I can't work without Visual Studio.
I've got Hyper-V working reliably under Windows 10 installed via Bootcamp on a 2016 MBP without TouchBar. The steps are relatively advanced, but were easy to follow and most people on this thread should be comfortable. You install and EFI boot manager called rEFInd (it's the 'modern' successor to a tool I used to use on my old MacBook Air called rEFIt).
By tinkering with rEFInd's configuration you can get it to EFI-boot Windows with the hypervisor enabled. Follow the instructions here, CAREFULLY: I also followed the steps in this article about enabling 'legacy safe mode' for Windows 10 (allowing me to press the F8 key during boot if anything goes wrong): The net result is a clean install of W10 via Bootcamp, with working Hyper-V. I need to use rEFInd as my boot manager to EFI-boot Windows, but that's totally fine in my book. I hope this helps people. I intend to cross post this solution on the other linked threads to get the word out there. Regards, Mark.