Visual Studio 2017 ServiceHub Exe's
-
When I start VS2017, before I even open a solution, there are 5 different EXE's that start: - ServiceHub.Host.CLR.x86.Exe - ServiceHub.Host.Node.x86.Exe - ServiceHub.IdentityHost.Exe - ServiceHub.SettingsHost.Exe - ServiceHub.VSDetouredHost.Exe They're using a fair amount of memory. Does anyone know what these are? Do they need to be running? If not, can I somehow keep them from starting? Thanks
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
When I start VS2017, before I even open a solution, there are 5 different EXE's that start: - ServiceHub.Host.CLR.x86.Exe - ServiceHub.Host.Node.x86.Exe - ServiceHub.IdentityHost.Exe - ServiceHub.SettingsHost.Exe - ServiceHub.VSDetouredHost.Exe They're using a fair amount of memory. Does anyone know what these are? Do they need to be running? If not, can I somehow keep them from starting? Thanks
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
Typically all of the components provided in Visual Studio 2017 have been properly shared in detail, so that you can easily get to know which of them do what. Anyways, if I (you could've as well :laugh: ) try to go a quick Google search for them, like the first one, we can find what they are, [.NET Framework service hosts for ServiceHub 1.0.226-rc](https://www.nuget.org/packages/Microsoft.ServiceHub.Host.CLR/) Also, Visual Studio 2017 allows you to easily change and update which of the programs or components get execute, when. So that you can cut them down when they start to take a lot of memory in the machine. For more please see: [Slow IDE performance working with Web projects - Developer Community](https://developercommunity.visualstudio.com/content/problem/30723/visual-studio-2017-too-slow-for-use.html)
The shit I complain about It's like there ain't a cloud in the sky and it's raining out - Eminem ~! Firewall !~
-
When I start VS2017, before I even open a solution, there are 5 different EXE's that start: - ServiceHub.Host.CLR.x86.Exe - ServiceHub.Host.Node.x86.Exe - ServiceHub.IdentityHost.Exe - ServiceHub.SettingsHost.Exe - ServiceHub.VSDetouredHost.Exe They're using a fair amount of memory. Does anyone know what these are? Do they need to be running? If not, can I somehow keep them from starting? Thanks
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
A small tool vs2017_serviceHubKiller does the trick. It support multiple instances of Visual Studio 2017. The tool temporarily deletes
"C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\ServiceHub\Hosts"
to trick VS.
-
A small tool vs2017_serviceHubKiller does the trick. It support multiple instances of Visual Studio 2017. The tool temporarily deletes
"C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\ServiceHub\Hosts"
to trick VS.
Detail of the issue Plus starting 2017 version 15.2, the high memory consumption issue is fixed.
World without walls neither need gates nor windows.