Visual Studio 2015 Update 1 spamming localhost

Visual StudioVisual Studio-2015

Visual Studio Problem Overview


I installed Visual Studio Update 1 yesterday and now when running ASP.NET services locally on IIS (not the express version). I am seeing hundreds of requests per second to the address

 http://localhost:49155/vshub/ca9dea4b016f45c68a6a8c1a07809eb4/DataWarehouseModule/dataWarehouse/getStatus/ 

What is causing this and is it preventable?

Visual Studio Solutions


Solution 1 - Visual Studio

Another option for preventing fiddler from chewing up your CPU is write a rule in fiddler to ignore those requests. Goto Rules > Customize Rules... find the function OnBeforeRequest and add

if(oSession.oRequest.headers["host"]=="localhost:49155"){
    oSession["ui-hide"] = "true";
}

so mine looks like this:

static function OnBeforeRequest(oSession: Session) {
	if(oSession.oRequest.headers["host"]=="localhost:49155"){
		oSession["ui-hide"] = "true";
	}
}

as @matrixugly pointed out the port can be different depending on the version of VS. @tedd-hansen's solution might be better across all versions of visual studio.

if(oSession.oRequest.headers["host"].StartsWith("localhost") 
    && oSession.PathAndQuery.StartsWith("/vshub/")) {
    oSession["ui-hide"] = "true";
}

Here's some discussion about this issue on github to get a better understanding of what's going on; https://github.com/aspnet/Mvc/issues/3655

Here's another post on SO for the same issue; https://stackoverflow.com/questions/33837163/visual-studio-2015-vshub-is-spamming-fiddler/33928841#33928841

Solution 2 - Visual Studio

This is the debugger sending information back to VSHub process. It's internal communication between the two processes so that part of the debugger data collection can happen out-of-process.

It helps with debugger tooltips, performance information, the historical debugging experience and more. As such there's no way to turn it off without seriously crippling the advanced debugger features.

You can turn some of these features off (though other features may still rely on Vshub to do out-of-process work in the background):

Tools > Options > Debugging > General > [  ] Enable Diagnostic Tools while debugging

The communication is purely local and doesn't pose a serious overhead or issue. Is there a specific reason you want to get rid of it? Tools like Fiddler can be configured to filter on process, so ignoring this traffic should be simple.

Solution 3 - Visual Studio

Since this has turned into ways to make Fiddler ignore the requests, the easiest way I've found is to go to the Filters tab, Request Headers section, check the "Hide if URL contains" box and enter "/vshub/".

Hiding with Filters

Solution 4 - Visual Studio

I realize this is not the answer, but it may help others that come here (like me).

Expanding on the answer KyleUp gave. Adding this to the "OnBeforeRequest" method is a bit more general and stops all localhost /vshub/ debug messages from filling up the view in Fiddler.

if(oSession.oRequest.headers["host"].StartsWith("localhost") 
   && oSession.PathAndQuery.StartsWith("/vshub/")) {
    oSession["ui-hide"] = "true";
}

Solution 5 - Visual Studio

This is an easier alternative to hide the vshub localhost traffic.

Go to Tools > Fiddler Options > Connections tab and add http://localhost:49155 to the bypass list. This will skip all traffic posted to that Url.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionFishcakeView Question on Stackoverflow
Solution 1 - Visual StudioKyleUpView Answer on Stackoverflow
Solution 2 - Visual StudiojessehouwingView Answer on Stackoverflow
Solution 3 - Visual StudioBrian ReischlView Answer on Stackoverflow
Solution 4 - Visual StudioTedd HansenView Answer on Stackoverflow
Solution 5 - Visual StudiomikroView Answer on Stackoverflow