Slowness, Hangings and Low Performance
To troubleshoot common Visual Studio problems please run Visual Studio executable file with /Log command Line switch and send us resulting log file.
Back to top
To collect additional logs generated by JetBrains dotCover, add
teamcity.agent.dotCover.log configuration parameter to the build configuration with a path to an empty directory on agent.
All dotCover log files will be placed there and TeamCity will publish zipped logs as hidden build artifact
On a rare occasion of TeamCity server or agent process terminating unexpectedly with no apparent reason, it can happen that this is caused by Java runtime crash.
If this happens, Oracle JVM creates a file named
hs_err_pid*.log in the working directory of the process. Working directory can be
<TeamCity server or agent home>/bin or other like
C:\Windows\SysWOW64. You can also search the disk for the recent files with "hs_err_pid" in the name.
See also related posting.