GCP Cloud Run container fails with Uncaught signal: 11 Segmentation fault - Node - Fastify

Question

I have a node server application using Fastify. I can build and run the image locally without a trouble. But when I deploy to the cloud, it fails to start and gives Uncaught signal: 11 - Segmentation fault. After doing some digging I found that it's due to a 3rd party library and problem goes away when I remove it. Library is https://www.npmjs.com/package/@transmute/vc.js

Not using the library is not an option unfortunately. Everything works fine locally but fails in the cloud. I tried different node versions from 14.18 to latest. Also I tried increasing container memory limit up to 1024Mi but no luck.

Anyone have an idea?

Answer 1

In my case, I was deploying a Python gRPC server in Google Cloud run and got the same Signal 11 error and terminated container.

What worked for me was setting the execution environment to gen2.

https://cloud.google.com/run/docs/about-execution-environments

Thanks to the comment by guillaume blaquiere.

Answer 2

Solved it by downgrading my node version from 18 to 16 (in the functions/package.json file)

Answer 3

Solved by increasing the memory limit to 2048Mi.