You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm pretty new to Next.js, and have recently started running into an issue while working on an app. This seems to happen about every 1-2 hours.
Application was created using create-next-app, and is using tailwind.
First, something (the renderer?) will run out of memory and crash, giving me this message on the console:
[0] - warn The server is running out of memory, restarting to free up memory.
[0] - wait compiling...
[0] TypeError: fetch failed
[0] at Object.fetch (node:internal/deps/undici/undici:11413:11)
[0] at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[0] at async invokeRequest (/Users/marlier/dev/cgn/roadmap/node_modules/next/dist/server/lib/server-ipc/invoke-request.js:17:12)
[0] at async invokeRender (/Users/marlier/dev/cgn/roadmap/node_modules/next/dist/server/lib/router-server.js:253:29)
[0] at async handleRequest (/Users/marlier/dev/cgn/roadmap/node_modules/next/dist/server/lib/router-server.js:446:24)
[0] at async requestHandler (/Users/marlier/dev/cgn/roadmap/node_modules/next/dist/server/lib/router-server.js:463:13)
[0] at async Server.<anonymous> (/Users/marlier/dev/cgn/roadmap/node_modules/next/dist/server/lib/start-server.js:117:13) {
[0] cause: Error: connect ECONNREFUSED ::1:60136
[0] at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1494:16) {
[0] errno: -61,
[0] code: 'ECONNREFUSED',
[0] syscall: 'connect',
[0] address: '::1',
[0] port: 60136
[0] }
[0] }
[0] - wait compiling /_error (client and server)...
[0] - event compiled client and server successfully in 2.2s (2044 modules)
[0] TypeError: fetch failed
[0] at Object.fetch (node:internal/deps/undici/undici:11413:11)
[0] at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[0] at async invokeRequest (/Users/marlier/dev/cgn/roadmap/node_modules/next/dist/server/lib/server-ipc/invoke-request.js:17:12)
[0] at async invokeRender (/Users/marlier/dev/cgn/roadmap/node_modules/next/dist/server/lib/router-server.js:253:29)
[0] at async handleRequest (/Users/marlier/dev/cgn/roadmap/node_modules/next/dist/server/lib/router-server.js:446:24)
[0] at async requestHandler (/Users/marlier/dev/cgn/roadmap/node_modules/next/dist/server/lib/router-server.js:463:13)
[0] at async Server.<anonymous> (/Users/marlier/dev/cgn/roadmap/node_modules/next/dist/server/lib/start-server.js:117:13) {
[0] cause: Error: connect ECONNREFUSED ::1:60136
[0] at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1494:16) {
[0] errno: -61,
[0] code: 'ECONNREFUSED',
[0] syscall: 'connect',
[0] address: '::1',
[0] port: 60136
[0] }
[0] }
[0] - info Loaded env from ...
Even after restart, the server does not work correctly and I need to exit the process.
When I restart, requests to the dev server return a 500, with this message on the console:
[0] Error: Cannot find module '../webpack-runtime.js'
[0] Require stack:
[0] - /Users/marlier/dev/cgn/roadmap/.next/server/pages/_document.js
[0] - /Users/marlier/dev/cgn/roadmap/node_modules/next/dist/server/require.js
[0] - /Users/marlier/dev/cgn/roadmap/node_modules/next/dist/server/next-server.js
[0] - /Users/marlier/dev/cgn/roadmap/node_modules/next/dist/server/dev/next-dev-server.js
[0] - /Users/marlier/dev/cgn/roadmap/node_modules/next/dist/server/next.js
[0] - /Users/marlier/dev/cgn/roadmap/node_modules/next/dist/server/lib/render-server.js
[0] - /Users/marlier/dev/cgn/roadmap/node_modules/next/dist/compiled/jest-worker/processChild.js
[0] at Module._resolveFilename (node:internal/modules/cjs/loader:1075:15)
[0] at /Users/marlier/dev/cgn/roadmap/node_modules/next/dist/server/require-hook.js:110:36
[0] at Module._load (node:internal/modules/cjs/loader:920:27)
[0] at Module.require (node:internal/modules/cjs/loader:1141:19)
[0] at require (node:internal/modules/cjs/helpers:110:18)
[0] at /Users/marlier/dev/cgn/roadmap/.next/server/pages/_document.js:120:27
[0] at Object.<anonymous> (/Users/marlier/dev/cgn/roadmap/.next/server/pages/_document.js:126:3)
[0] at Module._compile (node:internal/modules/cjs/loader:1254:14)
[0] at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
[0] at Module.load (node:internal/modules/cjs/loader:1117:32)
[0] at Module._load (node:internal/modules/cjs/loader:958:12)
[0] at Module.require (node:internal/modules/cjs/loader:1141:19)
[0] at require (node:internal/modules/cjs/helpers:110:18)
[0] at requirePage (/Users/marlier/dev/cgn/roadmap/node_modules/next/dist/server/require.js:112:75)
[0] at /Users/marlier/dev/cgn/roadmap/node_modules/next/dist/server/load-components.js:76:65
[0] at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[0] at async Promise.all (index 0)
[0] at async loadComponentsImpl (/Users/marlier/dev/cgn/roadmap/node_modules/next/dist/server/load-components.js:75:33)
[0] at async DevServer.findPageComponentsImpl (/Users/marlier/dev/cgn/roadmap/node_modules/next/dist/server/next-server.js:439:36) {
[0] code: 'MODULE_NOT_FOUND',
[0] requireStack: [
[0] '/Users/marlier/dev/cgn/roadmap/.next/server/pages/_document.js',
[0] '/Users/marlier/dev/cgn/roadmap/node_modules/next/dist/server/require.js',
[0] '/Users/marlier/dev/cgn/roadmap/node_modules/next/dist/server/next-server.js',
[0] '/Users/marlier/dev/cgn/roadmap/node_modules/next/dist/server/dev/next-dev-server.js',
[0] '/Users/marlier/dev/cgn/roadmap/node_modules/next/dist/server/next.js',
[0] '/Users/marlier/dev/cgn/roadmap/node_modules/next/dist/server/lib/render-server.js',
[0] '/Users/marlier/dev/cgn/roadmap/node_modules/next/dist/compiled/jest-worker/processChild.js'
[0] ]
[0] }
In order to recover, I have to do rm -rf .next && rm -rf node_modules && npm i. After doing so, the dev server will begin to work again. rm -rf .next is not sufficient, unfortunately.
I'm presuming that this has something to do with webpack configs, but I really don't understand how webpack works/interacts with Next.js well enough to debug.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
I'm pretty new to Next.js, and have recently started running into an issue while working on an app. This seems to happen about every 1-2 hours.
Application was created using create-next-app, and is using tailwind.
First, something (the renderer?) will run out of memory and crash, giving me this message on the console:
Even after restart, the server does not work correctly and I need to exit the process.
When I restart, requests to the dev server return a 500, with this message on the console:
In order to recover, I have to do
rm -rf .next && rm -rf node_modules && npm i. After doing so, the dev server will begin to work again.rm -rf .nextis not sufficient, unfortunately.I'm presuming that this has something to do with webpack configs, but I really don't understand how webpack works/interacts with Next.js well enough to debug.
Additional information
next.config.js:package.json:Beta Was this translation helpful? Give feedback.
All reactions