-
We saw a massive increase in memory in our next.js application after updating to version 20.16.0. We build our application with docker and the 20-alpine image. Other users were also able to confirm this problem: https://www.reddit.com/r/node/comments/1ejzn64/sudden_inexplicable_memory_leak_on_new_builds/ We then switched to version 20.15.1 and the memory returned to normal. Maybe someone else could confirm this problem too? |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 6 replies
-
Hi! Could you possibly narrow down where the error is coming from and provide a minimal reproducible example? Additionally, does this also occur on v22? |
Beta Was this translation helpful? Give feedback.
-
@redyetidev I was able to reproduce the issue locally and trace it back to this commit: 45c5ec8 the prior commit, e282925 works with no memory leak the next commit, 45c5ec8 causes a memory leak Something was introduced in undici between 6.15.0 and 6.16.1 which is causing issues |
Beta Was this translation helpful? Give feedback.
-
same issue, when using next.js application with node 20.16.0 on server we saw a massive increase in memory. upgrade to node 22.7.0 solved the issue |
Beta Was this translation helpful? Give feedback.
-
This is solver in Node.js v22.7.0. The fix will be available in the next v20 release too. |
Beta Was this translation helpful? Give feedback.
This is solver in Node.js v22.7.0. The fix will be available in the next v20 release too.