You are viewing the documentation of TeamCity 2018.x, which is not the most recently released version of TeamCity.
View this page in the latest documentation or refer to the listing to choose the documentation corresponding to your TeamCity version.


Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: related to https://youtrack.jetbrains.com/issue/TW-57431


If it is the TeamCity server that is loading the CPU/IO or there is no substantial CPU/IO load and everything runs just fine except for TeamCity, then this is to be investigated further.

Please check Check if you have any Conflicting Software like anti-virus running on the machine and disable/uninstall it.

If you have a substantial TeamCity installation, please check you have appropriate your memory settings as the first step.


During the slow operation, take several thread dumps of the slow process (see below for thread dump taking approaches) with 5-10 seconds interval. If the slowness continues, please take several more thread dumps (e.g. 3-5 within several minutes) and then repeat after some time (e.g. 10 minutes) while the process is still being slow.

Then send us a detailed description of the issue accompanied with the thread dumps and full server (or agent) logs covering the issue. Unless it is undesirable for some reason, the preferred way is to file an issue into our issue tracker and let us know via feedback email. Please include all the relevant details of investigation, including the CPU/IO load information, what specifically is slow and what is not, note URLs, visible effects, etc.
For large amounts of data, please use our FTP.

Server Thread Dump

When an operation on the server is slow, please take a set of the server thread dumps (10+) spread over the time of the slowness. TeamCity automatically saves thread dumps on super slow operations. , so there might already be some saved in logs/threadDumps-<date> directories.
It is recommended to send us an archive of the entire content of server's <TeamCity Home>/logs/threadDumps-<date> directories for all the recent dates.

It is recommended that you take a thread dump of the TeamCity server from the Web UI ( if the hanging is local and you can still open the TeamCity Administration pages): go to the Administration | Server Administration | Diagnostics page and click the Save Thread Dump button to save a dump under the <TeamCity Home>/logs/threadDumps-<date> directory (where you can later download the files from "Server Logs").
If the server is fully started but the web UI is not responsive, try the direct URL using the actual URL of your TeamCity server.


To capture logs from the TeamCity Visual Studio Addin, please run Microsoft Visual Studio executable (:

1. Locate the Visual Studio installation directory (in the example below c:\Program Files (x86)\Microsoft Visual Studio\2017\Common7\IDE)

2. Run Microsoft Visual Studio executable (INSTALLATION_DIRECTORY\Common7\IDE\devenv.exe) with additional from the command line with the ReSharper-related command line arguments:

  • For TeamCity VS Add-in as a part of ReSharper Ultimate use /ReSharper.LogFile <PATH_TO_FILE> and /ReSharper.LogLevel <Normal|Verbose|Trace> switches

    Code Block
    c:\Program Files (x86)\Microsoft Visual Studio\2017\Common7\IDE>devenv.exe /ReSharper.LogFile C:\Users\jetbrains\Desktop\vs.log /ReSharper.LogLevel Verbose
  • For Legacy version of TeamCity VS Add-in, use /TeamCity.LogFile <PATH_TO_FILE> and  /TeamCity.LogLevel <Normal|Verbose|Trace> switches

Visual Studio logging

To troubleshoot common Visual Studio problems please run , run Microsoft Visual Studio executable file with (INSTALLATION_DIRECTORY\Common7\IDE\devenv.exe) with the /Log command Line switch and send us resulting log file.