TypeError [ERR_INVALID_STATE]: Invalid state: ReadableStream is already closed

[willianrod]

Link to the code that reproduces this issue

https://github.com/willianrod/next-readable-stream-error

To Reproduce

1. Run the project locally
2. Go to /auth/login
3. The app will redirect you to /sample/list after resolving the promise
4. You should now see the error on your console

Current vs. Expected behavior

Current: Right now, when I'm navigating between pages with server components I'm seeing errors on my development console.
Expected: When navigating between pages no errors should be prompted

Verify canary release

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

Provide environment information

Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.5.0: Thu Jun  8 22:22:23 PDT 2023; root:xnu-8796.121.3~7/RELEASE_ARM64_T6020
    Binaries:
      Node: 18.16.0
      npm: 9.5.1
      Yarn: 1.22.19
      pnpm: 8.6.12
    Relevant Packages:
      next: 13.5.1
      eslint-config-next: 13.5.1
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.2.2
    Next.js Config:
      output: N/A

Which area(s) are affected? (Select all that apply)

App Router

Additional context

There is a discussion with more people with the same issue. The latest request was to update to the latest version 13.5.1 and see if the issue was still happening.

#55027

Internal error: TypeError [ERR_INVALID_STATE]: Invalid state: ReadableStream is already closed
    at new NodeError (node:internal/errors:399:5)
    at ReadableByteStreamController.enqueue (node:internal/webstreams/readablestream:1150:13)
    at /path/to/app/readable-error/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:1:447268
    at ut (/path/to/app/readable-error/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:1:447318)
    at ct (/path/to/app/readable-error/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:1:446596)
    at Timeout._onTimeout (/path/to/app/readable-error/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:1:443766)
    at listOnTimeout (node:internal/timers:569:17)
    at process.processTimers (node:internal/timers:512:7

[icyJoseph]

Looks like a form of this error started to happen after:

• next@13.4.13-canary.4

Could someone else double check by using next@13.4.13-canary.3, verify no error, and then use next@13.4.13-canary.4, to see the error?

[willianrod]

@icyJoseph yep, I can confirm that the error started after next@13.4.13-canary.4.

TypeError [ERR_INVALID_STATE]: Invalid state: Unable to enqueue
    at new NodeError (node:internal/errors:399:5)
    at transformStreamDefaultControllerEnqueue (node:internal/webstreams/transformstream:488:11)
    at TransformStreamDefaultController.enqueue (node:internal/webstreams/transformstream:301:5)
    at Timeout._onTimeout (/path/to/app/readable-error/node_modules/next/dist/server/stream-utils/node-web-streams-helper.js:166:32)
    at listOnTimeout (node:internal/timers:569:17)
    at process.processTimers (node:internal/timers:512:7) {
  code: 'ERR_INVALID_STATE'
}
- error unhandledRejection: TypeError [ERR_INVALID_STATE]: Invalid state: Unable to enqueue
    at new NodeError (node:internal/errors:399:5)
    at transformStreamDefaultControllerEnqueue (node:internal/webstreams/transformstream:488:11)
    at TransformStreamDefaultController.enqueue (node:internal/webstreams/transformstream:301:5)
    at Timeout._onTimeout (/path/to/app/readable-error/node_modules/next/dist/server/stream-utils/node-web-streams-helper.js:166:32)
    at listOnTimeout (node:internal/timers:569:17)
    at process.processTimers (node:internal/timers:512:7) {
  digest: undefined
}
- error TypeError [ERR_INVALID_STATE]: Invalid state: ReadableStream is already closed

If I would guess, the error is originated on pipeReadable

Diff between next@13.4.13-canary.3 and next@13.4.13-canary.4
v13.4.13-canary.3...v13.4.13-canary.4#diff-9be48534a043c68023eef0f61dacd526b677c70ee3b61807b9da74a279aba2e5R41

[icyJoseph]

Ah I had selected the wrong tags when comparing... 🤦‍♂️

I was deeply puzzled...

• Correct link v13.4.13-canary.3...v13.4.13-canary.4#diff-9be48534a043c68023eef0f61dacd526b677c70ee3b61807b9da74a279aba2e5R41

[Hardel-DW]

https://github.com/Hardel-DW/next-issue

Same problem with Suspense and "loading.tsx" file.

I encounter the same problem when I reload my page before the request is completed, resulting in error messages. If I quickly reload it several times, it seems that the requests accumulate. When I utilize "loading.tsx," the error appears to be different.

[FaryarKankash]

Same problem here
i don't use suspense in my layout but i use loading.tsx file
this error doesn't cause any problem in my build
(i update next to 13.5.1 but it's not fixing anything!)

[andycansdale]

Yup, we're seeing the same in 13.5.1. I've not been able to track down the source of the error.

[Hardel-DW]

Problem still present in 13.5.2

[fadjrie]

experiencing that problem, how to fix?

[jridgewell]

This should be fixed by facebook/react#27405

[cheryl-c-tirerack]

"next": "13.5.3-canary.1",

Still happens.

[igloo1505]

Has anyone noticed any actual negative effects from this? I'm working on two separate apps more or less simultaneously, and they're both experiencing this same error but both are performing as they should as far as I can tell, but it is a bit concerning...