To learn how to profile and resolve memory issues with your Gatsby site, please see Resolving Out-of-Memory Issues in our open source documentation.
Occasionally larger Gatsby sites, or moderately-sized sites with unusual characteristics, run into out-of memory errors during the Gatsby build process. If you were previously able to build your site successfully and consistently but, you are now encountering frequent memory errors, it's possible that:
- you recently introduced a change in your application that is memory intensive or causes a memory leak
- your site grew over time and slowly started exceeding memory limits for your plan level
For Case 1, you should explore your build history to pinpoint when the memory errors started. From there you can review the latest commits prior to when the memory errors started. Sometimes this can be traced back to a specific pull request merge commit.
For Case 2, you will need to consider upgrading to a higher tier builds plan. The Platform Limits article details memory available for each plan level.