TeamCity Server Java Runtime Insufficient Memory
Answered
Our TeamCity server sometimes encounters insufficient memory issue at the start of a build for a build configuration.
TeamCity Server Specs:
- TeamCity Server Version 2018.1.3 (build 58658)
- Running on AWS EC2 instance w. (2 vCPUs, 4.0 GiB Memory)
- 1.7 GB Total Heap
- 150 GiB Attached Root Device Volume
-
Java version: 1.8.0_181
- Java VM info: Java HotSpot(TM) 64-Bit Server VM
- Java Home path: /usr/lib/jvm/java-8-oracle/jre
- Server: Apache Tomcat/8.5.32
I've uploaded two log files for this, TeamCity server exception log & build log:
-
hs_err_pid29263.log
- School_-_iOS_iOS_-_Development_-_Hockey_-_Master_228.log
The build seems to fail on start when the server is collecting changes from our repository, seemingly a file that's large as ~40 MB. We do not have any files that are larger than that in the repository. Would you be able to help us get a solution for this issue so that we don't run into it again?
Please sign in to leave a comment.
Hi,
the out of memory error is actually being reported by git with a heap size of 512Mb rather than teamcity itself, as the fetch is started in a separate process. You can adjust the amount of memory available for git here: https://www.jetbrains.com/help/teamcity/git.html#Git-InternalProperties