nextjs - 💡(How to fix) Fix Unknown root exit status [1 comments, 2 participants]

The error only appears on one specific page, and that page is very heavy to load, which might be causing the problem.

TL;DR

The "unknown root exit" issue from react-dom.production.min.js might be related to a specific page's heavy load, and ignoring it in Sentry may not be recommended without further investigation.

Guidance

• Investigate the heavy page load as a potential cause of the issue, and consider optimizing the page's performance to see if it resolves the error.
• Review Sentry logs to understand the frequency and impact of the "unknown root exit" issue, and assess whether it's safe to ignore or requires further attention.
• Check the React documentation and release notes for version 18.3.0-canary-178c267a4e-20241218 to see if there are any known issues or bugs related to this error.
• Consider testing the page with a non-minified version of react-dom to see if the issue persists, which might help identify the root cause.

Notes

The lack of clear reproduction steps and limited information about the page's content and functionality makes it challenging to provide a more specific solution. Further investigation and debugging are necessary to determine the root cause of the issue.

Recommendation

Apply workaround: Ignore the error in Sentry for now, but continue to monitor its frequency and impact, and revisit the issue if it becomes more prevalent or starts causing noticeable problems.