David,
Here’s the link to the bug report. https://connect.microsoft.com/VisualStudio/feedback/details/1598784/excessive-memory-usage I received a reply from the VS team (pretty quickly) with a request for the mini dump. I’ve attached a dump (before and after the crash) to the bug report already, but that was about 2 weeks ago. I’m assuming (since it’s still marked as active) that they just haven’t managed to get back around to this yet. :) Ed. From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of David Kean Sent: Thursday, 13 August 2015 3:12 PM To: ozDotNet <ozdotnet@ozdotnet.com> Subject: RE: Visual Studio 2015 complaints Eddie, can you point me to the connect bug? If you haven’t already, can you create a dump of the process when memory usage is high (Attach to the process from another instance of Visual Studio, break into the debugger and then choose Save Dump As… -> Minidump with Heap) and then share that somewhere on the bug (OneDrive?) I’ll make sure the right team gets it. From: ozdotnet-boun...@ozdotnet.com <mailto:ozdotnet-boun...@ozdotnet.com> [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Eddie de Bear (Gmail) Sent: Wednesday, August 12, 2015 9:50 PM To: 'ozDotNet' <ozdotnet@ozdotnet.com <mailto:ozdotnet@ozdotnet.com> > Subject: RE: Visual Studio 2015 complaints I’ve lodged a bug through connect about VS2015.. Basically, VS is crashing when it runs out of memory (it’s a 32 bit app, and its crashing when it hits a little over 2.3gb of RAM).. Yep, that’s right, a single instance of VS 2015 using 2.3gb or RAM. The particular solution I’m having issues with is a WPF app with a bit over 250k lines of code. ** Just as a side note, VS 2013 used around 500MB for this same solution *** I’m not having any other issues with other solutions **** The 2.3GB is used within about an hour of serious work. That’s a lot of crashes each day.. From: <mailto:ozdotnet-boun...@ozdotnet.com> ozdotnet-boun...@ozdotnet.com [ <mailto:ozdotnet-boun...@ozdotnet.com> mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of David Kean Sent: Thursday, 13 August 2015 2:41 PM To: ozDotNet < <mailto:ozdotnet@ozdotnet.com> ozdotnet@ozdotnet.com> Subject: RE: Visual Studio 2015 complaints Thanks Greg. First is known and something we’re aware of, it will be fixed in the next VS Update. Second I’ve not heard, can you use the Send-A-Frown, we’re looking at these daily and this will get routed to the right team. From: <mailto:ozdotnet-boun...@ozdotnet.com> ozdotnet-boun...@ozdotnet.com [ <mailto:ozdotnet-boun...@ozdotnet.com> mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Greg Keogh Sent: Wednesday, August 12, 2015 9:33 PM To: ozDotNet < <mailto:ozdotnet@ozdotnet.com> ozdotnet@ozdotnet.com> Subject: Visual Studio 2015 complaints • It seems to be well known around the web that if you have the VS2015 options so C# Text Editor has "Keep Tabs" then F12 (go to definition) and Alt+F12 (peek definition) don't work. This may sound utterly absurd but it's true (it's like a link between slamming my car door causing it to rain). Unfortunately for me, I've had "Keep Tabs" on since it was invented. • In VS2013 I could Ctlr+Wheel to change the font size of individual windows. In VS2015 the font size of all open windows seems to be ganged together. This is also crippling me due to having two monitors of different resolutions. These two seemingly small issues about F12 and font sizing are driving me barking mad during the whole of my working day. If anyone has any insights or tricks about these issues I'd really like to hear from you. In the meantime I'll keep searching, but nothing useful so far. Greg K
