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. Best mac desktop for video editing. 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. ![]() Over the last few years Visual Studio Code has grow very popular over the open-source IDE market. VS Code was publicly released in 2015 and now used by 35% of all developers according to 2018. 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.
0 Comments
Leave a Reply. |