Project Keeps getting killed


#1

This is my project https://glitch.com/edit/#!/streamboy?path=new.js

It keeps stopping abruptly with the error:

/opt/watcher/app-types/node/start.sh: line 43: 16753 Killed node new.js

:weary:

How do I fix this?


#2

Hi :slight_smile:

it means that your project uses too much RAM. Does it use puppeteer perhaps?


#3

It doesn’t use Puppeteer. The ram usage stays below 50% most of the time.
And it doesn’t spike before getting killed.
I’ve linked the typical system usage during normal operation, and as it’s getting killed below.
usage


#4

does it spawn other processes? We limit the number of concurrent processes at 512 (minus system processes). Also, the monitor might not report the spike if it is too abrupt. After how long do you see app getting killed?


#5

It does not. And the app gets killed every couple of seconds. You can see it here


#6

It fixed itself (or you guys fixed it). I don’t know. Thanks anyway. :blush:

Never mind, it keeps doing that again.


#7

We recently changed how we enforce memory limits, so I am pretty sure that’s the case. I’ll look into it this Monday.

We allow up to 512MB of RAM for user projects; a spike in ram usage might not be reported by the monitor in the editor, but you might be able to see it by running htop in the console.


#8

Yeah, that’s probably it. I disabled this one and started a new project with fewer assets and modules, and everything seems to work fine. Thanks again.