nextjs - 💡(How to fix) Fix Next.js 16 entering an incorrect URL will cause a memory overflow and restart [15 comments, 9 participants]

TL;DR

The issue can likely be fixed by adjusting the Next.js configuration or the custom 404 page to handle non-existent routes without causing a memory overflow.

Guidance

• Verify that the custom 404 page (not-found.tsx) is correctly implemented and does not contain any infinite loops or recursive function calls that could cause a memory overflow.
• Check the Next.js documentation for any changes in handling non-existent routes in version 16 and update the configuration accordingly.
• Try to reproduce the issue with a minimal example to isolate the cause and test potential fixes.
• Consider adding error handling or a fallback mechanism to prevent the memory overflow when encountering non-existent routes.

Example

No specific code example can be provided without more information about the custom 404 page implementation.

Notes

The issue may be related to changes in Next.js 16, and the custom 404 page implementation might need to be updated to be compatible with the new version.

Recommendation

Apply a workaround by adjusting the custom 404 page implementation to handle non-existent routes without causing a memory overflow, as the issue is likely related to the specific implementation rather than a bug in Next.js 16.