Take garbage collector into account about java-buildpack-memory-calculator HOT 1 CLOSED

Thanks for reaching out. It's tricky to comment without some details about where the memory was being used. When you have situations like this, I would suggest doing the following:

1. Bump your memory limit up
2. Set the headroom to take up the amount you've increased the memory limit. This should give your app the same amount of memory but have a buffer of unallocated space to prevent your container from crashing.
3. Enable Java NMT and watch the memory usage, in particular as you approach the old memory limit and go past it. Java NMT is very detailed so it'll show you exactly where memory is growing and from there you can see exactly why you're going over the limit.

This is a pretty old issue (so sorry for the late reply). If you or someone else are still experiencing issues please follow the steps above, open a new issue and attach a few Java NMT diff's, making sure to indicate what your new & old memory limits are so we can see what is using up the memory. Thanks!

from java-buildpack-memory-calculator.