Bug: extremely high memory usage with `next dev`

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
  Platform: android
  Arch: arm64
  Version: #2 SMP PREEMPT Fri Aug 5 15:52:33 AST 2022
Binaries:
  Node: 18.10.0
  npm: 8.19.2
  Yarn: 1.22.19
  pnpm: N/A
Relevant packages:
  next: 13.0.3-canary.0
  eslint-config-next: 13.0.2
  react: 18.2.0
  react-dom: 18.2.0

What browser are you using? (if relevant)

Chrome Canary v109.0.5400.0 (Android)

How are you deploying your application? (if relevant)

Vercel

Describe the Bug

The memory usage on the last next 13 (13.0.3-canary.0 and 13.0.2) releases are too high. next dev command uses about 1gb of ram. Next 12 is using about 300mb-500mb’s of ram.

Expected Behavior

next dev should use less ram.

Link to reproduction

.

To Reproduce

1. Create project with Next 13
2. Run next dev
3. Check the ram usage

[feedthejim]

Another update:

• good news: I merged two fixes, so hopefully the next canary will help.
• bad news: there’s another memory leak that comes from Node itself which means that it’s gonna be very hard to fix. I’m currently exploring how we could work around the issue.
• bad news 2: i think I saw another memory leak linked to the edge runtime, so I’ll have to investigate that too.

[feedthejim]

hey, sorry I was busy investigating the issue!

Small update: I managed to identify the 3 main sources of memory leaks that I think are causing the crashes in dev so I’ll work on fixing those quickly. This should help a lot hopefully.

Thanks @soylemezali42 for the test app, it was very very helpful 🙏.