-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Frequent java.lang.OutOfMemoryError: Metaspace #26
Comments
arichiardi
added a commit
to arichiardi/boot
that referenced
this issue
Jun 23, 2016
This was particularly evident when doing `boot watch test` and has been fixed thanks to Micha's intuition of adding a clojure.core/shutdown-agents in boot.pod/destroy-pod. Fixes adzerk-oss/boot-test#26
arichiardi
added a commit
to arichiardi/boot
that referenced
this issue
Jun 23, 2016
This was particularly evident when doing `boot watch test` and has been fixed thanks to Micha's intuition of adding a clojure.core/shutdown-agents in boot.pod/destroy-pod. Fixes adzerk-oss/boot-test#26
arichiardi
added a commit
to arichiardi/boot
that referenced
this issue
Jun 29, 2016
In order to fix memory leaks in task-local pods, we need a way to execute custom cleaning at pod destroy time. This was particularly evident when doing `boot watch test` in a resource heavy app. Fixes adzerk-oss/boot-test#26
arichiardi
added a commit
to arichiardi/boot
that referenced
this issue
Jun 29, 2016
In order to fix memory leaks in task-local pods, we need a way to execute custom cleaning at pod destroy time. This was particularly evident when doing `boot watch test` in a resource heavy app. Fixes adzerk-oss/boot-test#26
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
When using
boot watch test
I have a very frequent error:I have not counted the time it takes but my feeling is every 20 mins of the tests running. I already have a pretty high configuration, which I gathered from the boot wiki (but might be off):
export BOOT_JVM_OPTIONS="-Xmx2g -client -XX:MaxMetaspaceSize=1g -XX:+TieredCompilation -XX:TieredStopAtLevel=1 -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -Xverify:none -XX:-OmitStackTraceInFastThrow"
What else can I tweak? I also briefly investigated if it was
pod/pod-pool
's fault in a way. It probably is, but I could not figure out way during my first attempt.The text was updated successfully, but these errors were encountered: