app killed with exit code 137
Hi, my project(id: ffc699a7-8a82-4231-949c-107a6fecfffc) was killed. However, it seems the memory, cpu and timeout didn't exceed the limit of my plan(hobby). could you please help me figure out the potential issue? Appreciate your help
Solution:Jump to solution
very good possibility that there was a resource spike that went above your plan limits, a spike fast enough that it wasn't caught by the metrics recording frequency
8 Replies
Project ID:
ffc699a7-8a82-4231-949c-107a6fecfffcwhat kind of app are you running?
Zero knowledge prover, it is computation intense
what do the metrics look like during the crash?
CPU: 0.3 vCPU
Memory: 200MB
Network: 45MB
Solution
very good possibility that there was a resource spike that went above your plan limits, a spike fast enough that it wasn't caught by the metrics recording frequency
I’m in hobby plans, I can run it on my laptop with 8GB ram. Not sure why it will exceed the limit. It’s so hard to debug
It’s killed after30 seconds even if I upgrade to pro plan. Is it the issue from timeout?
Ahhh it pass now. You are right! The spike of memory is 9GB exceeding my hobby plan limit. Appreciate your help 🙏🙏🙏
there really should be better feedback from the railway side of things, like a popup saying this service exceeded it's memory/cpu and was shut down kinda thing