We've experienced an annoying problem with our TFS 2010 Build Service. We have a dedicated build machine (Xeon X5550 and 3GB RAM) for Continuous Integration builds. We have a mid-size code-base with mixture of C# (~80%) and C++ (~20%) projects. The projects and solutions are VS 2008 format at the moment. Due the geographical distribution of our developers we have check-ins (so triggered CI builds) roughly consistent 24 hours per day. The problem we have is that after a day or two memory usage on that build machine goes up (while performance goes down) until in 2-3 days builds stuck. The memory consumption of TFSBuildSericeHost.exe Process at that moment is usually 2.3-2.4 GB. Restarting the TFSBuildServiceHost Service releases the memory and solves the problem for 1-2 days again.
Is it a known problem? Are there any solutions/workarounds for that?