a year ago
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
29 Replies
a year ago
Is this a template? Written by yourself? Language?
a year ago
Besides the deployments logging is there anything else we can look at
a year ago
Not a template, it's our API
a year ago
It's an expressJS server
a year ago
Did you make a specific change and then it started occuring?
a year ago
we changed out our logger and it started happning around 7 hours ago
a year ago
What is the memory spiking to? How do you know it's an OOM?
a year ago
But we cannot determine anything further, everything points to us doing things more efficiently vs less efficiently
a year ago
repeated Railway OOM errors and crashes
a year ago
What's the limit you have set
a year ago
4vCPU and 6GB memory
a year ago
2 replicas
a year ago
Anything that we can do to get more detailed information on Railway?
a year ago
(thanks for the prompt reply btw)
a year ago
Railway won't profile your application
a year ago
I'm not sure how I would debug this on Javascript
a year ago
yeah
a year ago
Is this app open source?
a year ago
no private API sorry i guess there isn't anything else we can get from railway and need to look at DD etc
a year ago
Yeah it's not really Railway's responsibility here
a year ago
I agree
a year ago
Thanks for trying to help
a year ago
Check for any added dependencies added to your project around the time the issue started happening
a year ago
Run the Dockerfile locally to see if it's happening there too
a year ago
a year ago
It’s a super hard problem because we think the errors were happening before but the OOM started after a huge logger refactor

a year ago
Going to try out the heap snapshot thanks @astrid(irl)*
a year ago
That's what you get for blindly trusing AI...
a year ago
Can also git bisect