4

I was happily debugging some C# code in Visual Studio 2015 when I started to notice that a VsHub related process (Microsoft.VsHub.HttpHost64.exe) was going bananas with memory consumption and slowing my whole system.

Memory consumption while debugging

and even after I close the application I was debugging and Visual Studio it still was consuming memory.

Memory consumption after VS closed

This keeps happening and makes debugging with Visual Studio a little bit frustrating... when this stuff is consuming more than twice the memory your own program is allocating.

Anyone having the same issue and solve it (without deleting/renaming the executable)? Any thoughts?

Raul Kist
  • 331
  • 3
  • 8
  • I have same problem - did you find a solution? – MojoDK Nov 29 '16 at 13:22
  • I too have the same problem and it only occurs with some projects. Microsoft did report that they had fixed the issue in Update 3, but it is still happening for me. Let's hope VS2017 (which comes out tomorrow) solves this issue. – xfx Mar 07 '17 at 01:49
  • Nope, just waiting for 2017 :( – Raul Kist Mar 07 '17 at 14:51

0 Answers0