[Out of memory: Java heap space] {build.status.text}
I get the below error after the build is done in Team city:
[Out of memory: Java heap space] {build.status.text}
And it does not trigger the next dependant build.
Teamcity version:TeamCity Enterprise 4.5.2.
Please help.
Please sign in to leave a comment.
I have set the memory as -Xmx1024m
Hi
Please take a look at OutOfMemory Problems page.
You may need to increase memory size to a build runner, not TeamCity server itself.
Michael
Ant runner is already 1024. but still the error. Its not a problem with all the configuration but jus two. so its not problem with the TC server.
Do you spawn some tests from the Ant? If so, chances are you have fork="yes" in JUnit task and in this case you need to increase memory given to JVM process running your tests.
No. we do not have junit testcase call.
Hi All,
I am also facing same issue, for me setting JVM arguments didn;t worked. Any help ? Did you anything more to resolve it ? We are using TC 6.0.1 version.
Even the addiotion of -XX:+HeapDumpOnOutOfMemoryError param is not helping to debug, no file is created for debug
Here is error:
[15:42:21]: [mail] Sending email: Hotfix Build 7.5.2 HF 10 build no. 690 is SUCESSFULL
[15:42:21]: [mail] Sent email with 1 attachment
[15:42:21]: Process exited with code 0
[15:42:21]: [Out of memory: Java heap space] {build.status.text}
[15:42:21]: [Out of memory: Java heap space] {build.status.text}
[15:42:21]: Publishing artifacts (running for 9h:58m:40s)
[15:42:21]: [Publishing artifacts] Paths to publish: [teamcity-info.xml]
[15:42:21]: [Publishing artifacts] Sending files
[15:42:21]: Build finished
Following is JVM settings in ant build step :
-Xms768m -Xmx1536m -XX:PermSize=256m -XX:MaxPermSize=512m
Following is JVM settings in agent.sh script:
TEAMCITY_AGENT_MEM_OPTS="-Xms1024m -Xmx1536m -XX:PermSize=256m -XX:MaxPermSize=512m -XX:+HeapDumpOnOutOfMemoryError
Regards,
Chetan
Chetan,
I've answered in http://devnet.jetbrains.net/message/5305094
Michael
Ramya,
Iа the issue is still actual, please take a memory dump as described in OutOfMemory Problems.