Hundreds of MSBuild and ConHost instances spawning and filling up memory when trying to run web Application in Visual Studio 2015 -


to give backstory, used have issue on vs2012 well. randomly (not time), when went run companies web project on ie via vs2012, stall while , fail load. noticed machine struggle anything, , come halt.

checking task manager reveal hundreds, if not thousands of msbuild.exe , conhost.exe instance spawned, filling every possible byte of memory (max 8 gigs on machine). had handful of solutions needed built.

i never found out real cause, eventual update vs2012 believe curbed issue several months.

fast forward today, on machine 16 gigs of ram , running vs2015 14.0.23107.

i noticed issue of the infinitely spawning msbuild , conhost back, time filling of 16 gigs of memory.

i have searched internet as can, have not found topics similar experiencing.

i know 'feature' microsoft, referenced here:

msbuild.exe staying open, locking files

and other places.

but no 1 have seen has problem many msbuilds , conhosts spawn every single byte of memory consumed them, , forced restart machine or wait until die (which doesn't seem happen after particular set amount of time).

the environment variables can think of when has happened are:

  1. i had @ least 2 instances of vs2015 running
  2. i had got done making changes , building 1 solution
  3. i went run our web application on solution depends on previous 1 had built.

does else have issue, , did ever find cause?

-edit-

update: not 100% if fixed it, haven't gotten since made these changes.

essentially, have 2 different solutions here @ work. similar, difference 1 of them has way less other projects/dependencies it.

i switch between these 2 solutions often, , believe solution config 1 of them had "debug extended diagnostics" checked @ least 1 project.

also, had build options set 8 parallel builds @ same time.

our devops manager thinks possible that, kind of switching between solutions mixed parallel builds caused kind of corruption/error spawned thousands of msbuilds.

we have since fixed problem "debug extended diagnostics" , have changed build options 1 parallel build , have not had issue since.

interestingly enough, had issue flood of msbuild , conhost processes started springing , killed memory. in case, related testing time zone features. changed os time zone testing/qa of web app , result reason. visual studio doesn't on-the-fly timezone changes.


Comments

Popular posts from this blog

php - Invalid Cofiguration - yii\base\InvalidConfigException - Yii2 -

How to show in django cms breadcrumbs full path? -

ruby on rails - npm error: tunneling socket could not be established, cause=connect ETIMEDOUT -