nextjs - 💡(How to fix) Fix PR #88577 fixes memory leak in canary but has not been backported to stable (16.2.2) [2 comments, 2 participants]

TL;DR

The most likely fix for the memory leak issue is to backport PR #88577 to the stable version of Next.js.

Guidance

• Verify that the memory leak is caused by the clone-response.ts file retaining ArrayBuffer references on every request, as mentioned in the issue.
• Check if upgrading to a version of Next.js that includes the fix from PR #88577 is feasible, considering the current version is 16.2.2.
• Consider applying a temporary workaround, such as increasing the Docker container's memory limit or implementing a custom solution to release the retained ArrayBuffer references.
• Review the changes made in PR #88577 to understand the root cause of the issue and potential implications of backporting the fix.

Example

No code snippet is provided as it is not explicitly supported by the issue.

Notes

The issue is specific to the standalone output mode of Next.js and the clone-response.ts file. The fix has been confirmed to work in the canary version, but it has not been backported to the stable version.

Recommendation

Apply workaround: Increase the Docker container's memory limit or implement a custom solution to release the retained ArrayBuffer references, as backporting PR #88577 to the stable version may take time.