How to debug & improve cache memory leak on Heroku?
Unanswered
Red-tailed wasp posted this in #help-forum
Red-tailed waspOP
Hey hey! I'm working on a Next.js 14 app ( https://hardcover.app/ ) that I recently tried migrating from Vercel to Heroku. The app was working well, but there's an issue with the memory usage: it'll grow until it exceeds the available memory of the process, then crash.
I'm wondering how to best debug this, find what's being cached, or where the memory leak is to best debug this. I've since moved the app back to Vercel (because it's crashing after 30 minutes on Heroku).
Anyone have any ideas on how to debug this to see why the memory usage of the app is climbing?
I'm wondering how to best debug this, find what's being cached, or where the memory leak is to best debug this. I've since moved the app back to Vercel (because it's crashing after 30 minutes on Heroku).
Anyone have any ideas on how to debug this to see why the memory usage of the app is climbing?
1 Reply
@Red-tailed wasp Hey hey! I'm working on a Next.js 14 app ( https://hardcover.app/ ) that I recently tried migrating from Vercel to Heroku. The app was working well, but there's an issue with the memory usage: it'll grow until it exceeds the available memory of the process, then crash.
I'm wondering how to best debug this, find what's being cached, or where the memory leak is to best debug this. I've since moved the app back to Vercel (because it's crashing after 30 minutes on Heroku).
Anyone have any ideas on how to debug this to see why the memory usage of the app is climbing?
have a look at https://github.com/vercel/next.js/issues/49929