Memory leak updating 13.4.12 to 13.4.16.

[VVIERV00]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Info after downgrade:
    Operating System:
      Platform: linux
      Arch: x64
      Version: #26~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Jul 13 16:27:29 UTC 2
    Binaries:
      Node: 20.5.1
      npm: 9.8.0
      Yarn: N/A
      pnpm: N/A
    Relevant Packages:
      next: 13.4.12
      eslint-config-next: 13.4.12
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 4.9.5
    Next.js Config:
      output: N/A


warn  - Latest canary version not detected, detected: "13.4.12", newest: "13.4.16".
        Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
        Read more - https://nextjs.org/docs/messages/opening-an-issue

Which area(s) of Next.js are affected? (leave empty if unsure)

Middleware / Edge (API routes, runtime)

Link to the code that reproduces this issue or a replay of the bug

I don't know how to efficiently provide a code example

To Reproduce

Deploy a Next.js app to Google Cloud Run using the Firebase framework. Due to an unresolved bug with Firebase hosting, it's recommended to access the app via Cloud Run. Please compare the memory usage and logs between versions 13.4.12 and 13.4.16. I suspect this issue may also surface on other hosting platforms.

Describe the Bug

I deployed my app on Google Cloud Run. After an update I made yesterday, the app completely crashed. Here are the logs:

• 'Memory limit of 512 MiB exceeded with 547 MiB used. Consider increasing the memory limit, see https://cloud.google.com/functions/docs/configuring/memory'
• "(node:1) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGTERM listeners added to [process]. Use emitter.setMaxListeners() to increase limit"
• "The request failed because either the HTTP response was malformed or connection to the instance had an error. Additional troubleshooting documentation can be found at: https://cloud.google.com/run/docs/troubleshooting#malformed-response-or-connection-error While handling this request, the container instance was found to be using too much memory and was terminated. This is likely to cause a new container instance to be used for the next request to this revision. If you see this message frequently, you may have a memory leak in your code or may need more memory. Consider creating a new revision with more memory.

Expected Behavior

Normal memory usage, no memory leaks and the app working fine.

Which browser are you using? (if relevant)

Version 115.0.5790.170 (Official Build) (64-bit)

How are you deploying your application? (if relevant)

Firebase frameworks support for next js

[balazsorban44]

Hi, could you post your application code or any kind of reproduction in #49929 as outlined in #49929 (comment)? 🙏 It's unactionable to investigate the issue otherwise.

[github-actions]

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.