We upgraded from 2017.2 and are now running the latest TeamCity (v2019) on a windows machine with the agent and server running as a service.
The server connects to a MS SQL 2016 instance.
When running, the SQL activity monitor shows 5 TeamCity applications/connections running. The memory usage for each session continues to grow. Over time this begins to negatively affect other database queries. At one time the connection(s) were using upwords of 1GB of memory each within SQL. with no active builds going on.
This happened in the 2017.2 version and is still happening in the 2019 version. If we restart the server service everything refreshes and the memory drops to 0 and then starts to grow again.
Please note we only have about 7 projects in TeamCity that build roughly once a week at most.
Is this a memory leak or is there a setting that tells teamcity to close its connections that I am missing?