running into a weird memory issue with our Next.js 16.2.9 setup
Unanswered
Parwar Yassin posted this in #help-forum
When I run pnpm --filter web dev (or pnpm dev), the next-server process immediately balloons to ~12GB of RAM within 20 seconds. it goes until 19 even!
Setup:
- Monorepo with pnpm + Turborepo
- Next.js 16.2.9 with React 19 (React Compiler already disabled for test)
- Convex backend (cloud, not local)
What I've tried:
- Disabled React Compiler ✗ (still spikes)
- Disabled Turbopack ✗ (still spikes)
- Cleared .next, node_modules/.turbo ✗ (still spikes)
- Ran just the web app in isolation ✗ (still spikes)
Wondering if it's a Turbopack or Next.js 16.2.9 regression, or something in our dependency tree. Anyone else hitting this?
i know for sure this is not normal by the way the project is quite big,
Setup:
- Monorepo with pnpm + Turborepo
- Next.js 16.2.9 with React 19 (React Compiler already disabled for test)
- Convex backend (cloud, not local)
What I've tried:
- Disabled React Compiler ✗ (still spikes)
- Disabled Turbopack ✗ (still spikes)
- Cleared .next, node_modules/.turbo ✗ (still spikes)
- Ran just the web app in isolation ✗ (still spikes)
Wondering if it's a Turbopack or Next.js 16.2.9 regression, or something in our dependency tree. Anyone else hitting this?
i know for sure this is not normal by the way the project is quite big,
7 Replies
it would like use up all my memory then crash
but deleting .next would fix it
I have also tried to see if it is still like that but it has not fixed and by the way, it is still like that project is starting to become unusable
my mac is MacBook pro m2 pro with 16gb
How big was your project?
that is mine