Like I said before, my lambda is running out of memory… apparently I have a memory leak, once the function instance is UP (after a cold start) it starts to consume more and more memory. How is supposed that I can debug this kind of issues? that’s my problem with Lambda.. I don’t see an official way to debug or profile this. 😞 On this screenshot, you can see, from bottom to top, that my lambda starts to consume more and more memory on each request… after it reaches 512MB and crashes (that’s my limit).

It's unlikely to be a lambda specific thing which means you should be able reproduce running the function outside the lambda environment. The first thing I'd look at is how you're caching things outside of your handler, these are the things that will be kept around between invocations.

I do agree that it’s annoying to debug these. There should be better tooling for this. What would be the ideal way to deal with issues like this?

Some useful information here https://www.toptal.com/nodejs/debugging-memory-leaks-node-js-applications

@Jay we need a sort of profiler, I’m looking into v8-profiler and others, but there is nothing plug and play. Definitely a gap here were the community should create something.

@Adrián Mouly agreed. Let me just put this on @Frank’s radar as well.

Great guys, you both are so awesome.

@Jay does it make sense if

sst start

had a flag to run with a built-in profiler on?

Oh, that’s a pretty interesting idea.

@Jay yeah we need this! move it to high priority. 😂

lol Yup opened an issue for this https://github.com/serverless-stack/serverless-stack/issues/539

😍