May 13, 2014

Grails R14 Error (Memory quota exceeded) on Heroku

I have frequently encountered the following Error R14 (Memory quota exceeded) in the logs while running Grails apps on Heroku on the 1x Dyno which only allows 512mb of RAM:

2014-05-08T04:46:48.294887+00:00 heroku[web.1]: Process running mem=557M(108.9%)
2014-05-08T04:46:48.295268+00:00 heroku[web.1]: Error R14 (Memory quota exceeded)

To debug the issue and to be sure I was not having an application specific error, I created a new Grails application and followed the “Getting Started with Grails on Heroku” tutorial, but I still was getting the R14 error with a new application. To debug how much memory was being used, I used the Application Info plugin and ran the new application on Heroku. The source for this application can be found on Github.

I tried to run the same build and server process as Heroku locally but found about a 100mb difference in memory usage. The only difference I had locally was using JDK7. So, I configured the project to use JDK7 on Heroku by add adding a “” file to the project with the JDK configuration as described in the Heroku Grails tutorial:

After starting up with the new JDK, I no longer say the Error R14 in the logs.

Using JDK7 on Heroku, the Grails application used much less memory on startup (454 vs 582 mb) and under load (496 vs 643 mb) using Apache Bench.

About the Author

Object Partners profile.

One thought on “Grails R14 Error (Memory quota exceeded) on Heroku

  1. jogee says:

    Greaatt!! Thanks man!

  2. Jean says:

    Thanks a lot, man. I had the same problem and was easilly solve by your solution.

  3. Geert Jonker says:

    Thanks, helped me a lot. My 2X Dyno with Grails app went from 1024MB to 624MB.
    Still, my Java Heap is only 364Mb, I’m wondering where all the other Mb’s are going to…

  4. Klemens says:

    In my case, changing from Tomcat to Jetty seemed to help with the memory issue. So the system property looks like this:


  5. I had to switch to Java 8 (java.runtime.version=1.8) to resolve this problem in my Grails app.

Leave a Reply

Your email address will not be published. Required fields are marked *

Related Blog Posts
Using Conftest to Validate Configuration Files
Conftest is a utility within the Open Policy Agent ecosystem that helps simplify writing validation tests against configuration files. In a previous blog post, I wrote about using the Open Policy Agent utility directly to […]
SwiftGen with Image & Color Asset Catalogs
You might remember back in 2015 when iOS 9 was introduced, and we were finally given a way to manage all of our assets in one place with Asset Catalogs. A few years later, support […]
Tracking Original URL Through Authentication
If you read my other post about refreshing AWS tokens, then you probably have a use case for keeping track of the original requested resource while the user goes through authentication so you can route […]
Using Spring Beans in a Kafka Streams ExceptionHandler
There are many things to know before diving into Kafka Streams. If you haven’t already, check out these 5 things as a starting point. Bullet 2 mentions designing for exceptions. Ironically, this seems to be […]