#Repeated Out of Memory crashes

29 messages · Page 1 of 1 (latest)

jade gale
#

Hi Team

Need help diagnosing what is causing the out of memory crashes on our API - Been pulling out our hair last 8 hours

Project: 7f34b4f7-9d09-48a8-997c-32a10e59c1eb

We have some errors from various functions but hard to pinpoint what is spiking the memory

vast shadow
#

Is this a template? Written by yourself? Language?

jade gale
#

Besides the deployments logging is there anything else we can look at

#

Not a template, it's our API

#

It's an expressJS server

vast shadow
#

Did you make a specific change and then it started occuring?

jade gale
#

we changed out our logger and it started happning around 7 hours ago

vast shadow
#

What is the memory spiking to? How do you know it's an OOM?

jade gale
#

But we cannot determine anything further, everything points to us doing things more efficiently vs less efficiently

#

repeated Railway OOM errors and crashes

vast shadow
#

What's the limit you have set

jade gale
#

4vCPU and 6GB memory

#

2 replicas

#

Anything that we can do to get more detailed information on Railway?

#

(thanks for the prompt reply btw)

vast shadow
#

Railway won't profile your application

#

I'm not sure how I would debug this on Javascript

jade gale
#

yeah

vast shadow
#

Is this app open source?

jade gale
#

no private API sorry i guess there isn't anything else we can get from railway and need to look at DD etc

vast shadow
#

Yeah it's not really Railway's responsibility here

jade gale
#

I agree

#

Thanks for trying to help

amber arch
#

Run the Dockerfile locally to see if it's happening there too

jade gale
#

It’s a super hard problem because we think the errors were happening before but the OOM started after a huge logger refactor

#

Going to try out the heap snapshot thanks @amber arch

vast shadow