Java process killed due to out of memory after running job in container for an hour

Build Environment
1

Hi CircleCI,

Java process killed due to out of memory after running job in container for an hour.

I have setup a job for running automation tests in CircleCI (https://hub.docker.com/r/jiteshsojitra/docker-headless-vnc-container), it works fine but after running tests for an hour it reaches to memory limit and suddenly kills running java/ant job. So is there any way to increase the memory so tests can run for 5-6 hours in container or its paid feature? Can someone please reply who experienced this problem and found some solution?

I tried by putting “- JAVA_OPTS: -Xms512m -Xmx1024m” in yml script but overall container memory size reaches to ~4GB as it looks like.

References:

https://circleci.com/gh/jiteshsojitra/zm-selenium/231
https://circleci.com/api/v1.1/project/github/jiteshsojitra/zm-selenium/231/output/106/0?file=true

Log trail:

BUILD FAILED
/headless/zm-selenium/build.xml:348: Java returned: 137

Total time: 76 minutes 26 seconds
Exited with code 137

Hint: Exit code 137 typically means the process is killed because it was running out of memory
Hint: Check if you can optimize the memory usage in your app
Hint: Max memory usage of this container is 4286337024
according to /sys/fs/cgroup/memory/memory.max_usage_in_bytes
2

(Aside: for general question readability, console IO can be rendered in inline code using backticks, and console output

can be rendered in block formatting using the toolbar icon
in the editor).
1 Like
3

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.