Gatsby Cloud build error 137

[hk86]

Hi there,

since yesterday I'm not able to build on Gatsby Cloud. Everything seems to run as always, but during page queries are run I get:

11:23:37 AM:
/usr/local/bin/runner-command: line 25:  4051 Killed                  ${GATSBY} build --no-color
11:23:37 AM:
ERROR Failed to compile: Error: Exited with code 137

137 seems to be an out of memory error. Locally everything works fine, I can build on Netlify as well.

I use Gatsby v3. The only change I commited was to add a process.env.GATSBY_VAR on my client side code in one of my components.

Any ideas what might cause the issue? Was there a change on Gatsby Cloud?

Best regards,
HK

[LekoArts]

For Gatsby Cloud support please reach out here: https://www.gatsbyjs.com/support/
Thanks!

[hk86]

Thanks

[gentksb]

I'm facing the same problem. It maybe cause by GatsbyCloud free plan limit, but limits doesn't works well I think.

My v2 blog and v3 small website got the out-of-memory error.
Locally, gatsby-plugin-inspecter result is under 1GB Heap RAM.

The only thing we can do is to inform GatsbyCloud support.

[gentksb]

Today, my lighter website completes build successfully. But another is not.

[hk86]

There is a 1GB memory limit on the free plan. This is causing the issue for me.

[hk86]

The must have changed it recently.

[fnebenfuehr]

We are having the same issue since we upgraded to gatsbyjs 3.0. Switching to the performance plan does fix it temporarily.

[daydream05]

Running into the same issue. It'd be nice if there's a guide to find out which causes 1gb of RAM usage for gatsby builds and what we can do to lower it.