Process killed even after upgrading to Developer plan
I was getting a 'killed' message when trying to run a process that takes some memory. I upgraded to the developer plan but still get the error. The logs show a spike to 2G but nowhere close to the 8G limit.
ServiceID: 548797fa-9e1b-486c-b816-1d7c3f8577a9
ServiceID: 548797fa-9e1b-486c-b816-1d7c3f8577a9
10 Replies
Project ID:
548797fa-9e1b-486c-b816-1d7c3f8577a9show the error messages please?
it just says 'killed' in the railway logs. i get a 503 from the client
show me?
if it was getting killed by railway, it wouldn't look like that, perhaps you are running into the default heap size of nodejs
you can try increasing the default heap size
its a python app. works when i run it locally so i dont think its a RAM issue.
it wouldn't be an issue with railway, it would be an issue with your app
does python have max memory defaults that you could increase?
if you're saying it's not a Railway issue, i'll start looking at ways to better optimize the call. i'm using a large language model pre-loaded into memory, but i will try to write to disk and call that way instead.
I'm confident that railway is not killing your app at this point, yes