Those of you who use devenv for building VS solutions(although you are discouraged to [here][1]) might get into trouble if your solution has more than 1 project and it takes quite a time building both. Today I had a problem with that launching VS build from inside an ant script – a standard windows crash appeared with 0xc000005 error code and a “friendly” Send/Don’t send error to Microsoft dialog. Also I noticed that the VS cl.exe compiler process is hanging after this crash, waiting for infinity.
Googling around led me to [this hm… page][2] after I thoroughly read the [very one microsoft forum thread about the issue][3]. The culprit is that you have to use 1 thread for all your compiling. Reposting from the last link you have to
set “maximum number of parallel project builds” to 1 instead of 2 or more, it doesn’t crash anymore.
explanation – a memory leak in the building module…
This actually doesn’t have to reproduce in SP1. I’ve got the latest VS Team developer with the latest SP and it still reproduces… Will try msBuild tomorrow and see if situation improves having more threads as the way it had been mentioned in the above links – if you have multi-core architecture you probably don’t want to do everything in one thread, especially if this is your continuous integration server.