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

willianrod · 2023-09-19T19:17:47Z

Link to the code that reproduces this issue

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

To Reproduce

Run the project locally
Go to /auth/login
The app will redirect you to /sample/list after resolving the promise
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

The text was updated successfully, but these errors were encountered:

icyJoseph · 2023-09-19T20:47:11Z

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

[email protected]

Could someone else double check by using [email protected], verify no error, and then use [email protected], to see the error?

willianrod · 2023-09-19T21:21:06Z

@icyJoseph yep, I can confirm that the error started after [email protected].

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 [email protected] and [email protected]
v13.4.13-canary.3...v13.4.13-canary.4#diff-9be48534a043c68023eef0f61dacd526b677c70ee3b61807b9da74a279aba2e5R41

icyJoseph · 2023-09-19T21:27:03Z

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 · 2023-09-19T22:27:16Z

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 · 2023-09-20T05:46:49Z

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 · 2023-09-20T14:36:37Z

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 · 2023-09-20T17:30:13Z

Problem still present in 13.5.2

fadjrie · 2023-09-20T19:08:47Z

experiencing that problem, how to fix?

jridgewell · 2023-09-22T04:04:27Z

This should be fixed by facebook/react#27405

cheryl-c-tirerack · 2023-09-22T14:51:58Z

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

Still happens.

igloo1505 · 2023-09-25T23:01:40Z

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...

wriddhi · 2023-09-26T07:40:17Z

@igloo1505 I'm facing this issue too but without having downsides in performance or code execution flow. I'm building an application for production. Have you seen/felt any real consequences/crashes issue with this yet or found a workaround? I really don't wanna rollback next to 13.4.5.

huozhi · 2023-09-26T14:03:30Z

Should be fixed by #56012 which carried the react change

rexedge · 2023-09-26T14:58:50Z

I am facing the same issue but my app works fine.

amyfranz · 2023-09-27T13:05:58Z

I'm also still getting it on Next.js 13.5.3

huozhi · 2023-09-27T17:53:46Z

The fix is landed in 13.5.4-canary.2

cheryl-c-tirerack · 2023-09-27T18:45:53Z

upgraded to 13.5.4-canary.2

still I get

jridgewell · 2023-09-27T20:19:22Z

@cheryl-c-tirerack That's a different issue, it just happen to originate from the same file. I'm not sure where we need to handle it.

huozhi · 2023-09-27T20:28:17Z

@cheryl-c-tirerack would be possible for you to file a reproduction in new issue? That would be super helpful for investigation 🙏

cheryl-c-tirerack · 2023-09-27T21:50:52Z

@cheryl-c-tirerack would be possible for you to file a reproduction in new issue? That would be super helpful for investigation 🙏

I wouldn't begin to know what to reproduce minimally. I have a full backend running locally, and many nested dynamic paths-- all proprietary. I'm using app directory, with TanStack/react-query.
It happens on any page that touches my api.
Exactly as the original issue, my api calls are in server components.
It happens right after navigating to a new endpoint.
The description and the error are exactly as shown on this OP, without any authorization.

dstarosta · 2023-09-27T23:47:27Z

upgraded to 13.5.4-canary.2

still I get

I get the same issue as well. When I run Playwright tests it happens in the same place the old error was happening.

Dev-Harmattan · 2023-09-28T10:54:36Z

I get the same issue. is there any fix for this ?
⨯ Internal error: TypeError [ERR_INVALID_STATE]: Invalid state: ReadableStream is already closed at new NodeError (node:internal/errors:405:5) at ReadableByteStreamController.enqueue (node:internal/webstreams/readablestream:1152:13) at /Users/sodiq/Desktop/potfolio-project/discord-app/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:1:461602

V-iktor · 2023-09-28T14:09:41Z

I get the same issue. is there any fix for this ?
⨯ Internal error: TypeError [ERR_INVALID_STATE]: Invalid state: ReadableStream is already closed at new NodeError (node:internal/errors:405:5) at ReadableByteStreamController.enqueue (node:internal/webstreams/readablestream:1152:13) at /Users/sodiq/Desktop/potfolio-project/discord-app/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:1:461602

Try updating to the latest React canary - now I get the correct error message instead of ERR_INVALID_STATE

yarn add [email protected]

The correct message I get after upgrading

TypeError: fetch failed

luistak · 2023-09-29T07:20:06Z

Same here on 13.5.2 but debugging the error stacktrace i caught that this error occurs in this order:

`Server component Loading
Error: The render was aborted by the server without a reason.

Error: The render was aborted by the server without a reason.
    at nR (/app/app/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:45:67960)
    at Object.cancel (/app/app/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:45:71720)
    at readableByteStreamControllerCancelSteps (node:internal/webstreams/readablestream:3022:37)
    at [kCancel] (node:internal/webstreams/readablestream:1166:12)
    at ensureIsPromise (node:internal/webstreams/util:192:19)
    at readableStreamCancel (node:internal/webstreams/readablestream:1887:5)
    at node:internal/webstreams/readablestream:1439:15
    at complete (node:internal/webstreams/readablestream:1323:9)
    at shutdownWithAnAction (node:internal/webstreams/readablestream:1319:5)
    at node:internal/webstreams/readablestream:1438:14
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

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

TypeError [ERR_INVALID_STATE]: Invalid state: ReadableStream is already closed
    at new NodeError (node:internal/errors:405:5)
    at ReadableByteStreamController.enqueue (node:internal/webstreams/readablestream:1152:13)
    at u (/app/app/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:45:486)
    at nP (/app/app/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:45:67693)
    at nR (/app/app/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:45:68650)
    at Object.cancel (/app/app/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:45:71720)
    at readableByteStreamControllerCancelSteps (node:internal/webstreams/readablestream:3022:37)
    at [kCancel] (node:internal/webstreams/readablestream:1166:12)
    at ensureIsPromise (node:internal/webstreams/util:192:19)
    at readableStreamCancel (node:internal/webstreams/readablestream:1887:5)
    at node:internal/webstreams/readablestream:1439:15
    at complete (node:internal/webstreams/readablestream:1323:9)
    at shutdownWithAnAction (node:internal/webstreams/readablestream:1319:5)
    at node:internal/webstreams/readablestream:1438:14
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

SocketError: other side closed

node:internal/deps/undici/undici in TLSSocket.onSocketEnd at line 9790:26
In App
node:events in TLSSocket.emit at line 526:35
In App
node:domain in TLSSocket.emit at line 489:12
In App
Called from: /app/app/node_modules/dd-trace/packages/datadog-instrumentations/src/net.js in TLSSocket.emit
node:internal/streams/readable in endReadableNT at line 1359:12
In App
node:internal/process/task_queues in process.processTicksAndRejections at line 82:21

Which Sentry identified that may be related to this other issue #49896:

Zanzofily · 2023-10-06T13:45:40Z

I tried updating next and node to the latest versions, but the error was still present. It seems to be related to how caching is handled. Changing caching to dynamic worked for me.

export const dynamic = 'force-dynamic'

amiryxe · 2023-10-06T14:42:00Z

I get this error when I refresh a page quickly and one after another.

DevOkone · 2023-10-08T12:20:50Z

Je reçois aussi le problème sur Next.js 13.5.3 mais j'ai l'impression que l'erreur ce déclenche lorsque j'utilise suspense sur une page
mais le code fonctionne bien en production

github-actions · 2023-10-23T00:03:55Z

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.

willianrod added the bug Issue was opened via the bug report template. label Sep 19, 2023

icyJoseph mentioned this issue Sep 20, 2023

fix: Invoke cancel, only if the stream is not closed #55684

Merged

huozhi closed this as completed in #55684 Sep 21, 2023

ztanner reopened this Sep 21, 2023

huozhi closed this as completed Sep 26, 2023

zawarudo mentioned this issue Oct 21, 2023

Integrate e2e with playwright bestofjs/bestofjs#223

Merged

github-actions bot added the locked label Oct 23, 2023

github-actions bot locked as resolved and limited conversation to collaborators Oct 23, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

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

willianrod commented Sep 19, 2023 •

edited

Loading

icyJoseph commented Sep 19, 2023

willianrod commented Sep 19, 2023

icyJoseph commented Sep 19, 2023 •

edited

Loading

Hardel-DW commented Sep 19, 2023 •

edited

Loading

FaryarKankash commented Sep 20, 2023 •

edited

Loading

andycansdale commented Sep 20, 2023

Hardel-DW commented Sep 20, 2023

fadjrie commented Sep 20, 2023

jridgewell commented Sep 22, 2023

cheryl-c-tirerack commented Sep 22, 2023 •

edited

Loading

igloo1505 commented Sep 25, 2023

wriddhi commented Sep 26, 2023

huozhi commented Sep 26, 2023

rexedge commented Sep 26, 2023

amyfranz commented Sep 27, 2023

huozhi commented Sep 27, 2023

cheryl-c-tirerack commented Sep 27, 2023 •

edited

Loading

jridgewell commented Sep 27, 2023

huozhi commented Sep 27, 2023

cheryl-c-tirerack commented Sep 27, 2023 •

edited

Loading

dstarosta commented Sep 27, 2023

Dev-Harmattan commented Sep 28, 2023

V-iktor commented Sep 28, 2023

luistak commented Sep 29, 2023

Zanzofily commented Oct 6, 2023 •

edited

Loading

amiryxe commented Oct 6, 2023 •

edited

Loading

DevOkone commented Oct 8, 2023

github-actions bot commented Oct 23, 2023

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

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

Comments

willianrod commented Sep 19, 2023 • edited Loading

Link to the code that reproduces this issue

To Reproduce

Current vs. Expected behavior

Verify canary release

Provide environment information

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

Additional context

icyJoseph commented Sep 19, 2023

willianrod commented Sep 19, 2023

icyJoseph commented Sep 19, 2023 • edited Loading

Hardel-DW commented Sep 19, 2023 • edited Loading

FaryarKankash commented Sep 20, 2023 • edited Loading

andycansdale commented Sep 20, 2023

Hardel-DW commented Sep 20, 2023

fadjrie commented Sep 20, 2023

jridgewell commented Sep 22, 2023

cheryl-c-tirerack commented Sep 22, 2023 • edited Loading

igloo1505 commented Sep 25, 2023

wriddhi commented Sep 26, 2023

huozhi commented Sep 26, 2023

rexedge commented Sep 26, 2023

amyfranz commented Sep 27, 2023

huozhi commented Sep 27, 2023

cheryl-c-tirerack commented Sep 27, 2023 • edited Loading

jridgewell commented Sep 27, 2023

huozhi commented Sep 27, 2023

cheryl-c-tirerack commented Sep 27, 2023 • edited Loading

dstarosta commented Sep 27, 2023

Dev-Harmattan commented Sep 28, 2023

V-iktor commented Sep 28, 2023

luistak commented Sep 29, 2023

Zanzofily commented Oct 6, 2023 • edited Loading

amiryxe commented Oct 6, 2023 • edited Loading

DevOkone commented Oct 8, 2023

github-actions bot commented Oct 23, 2023

willianrod commented Sep 19, 2023 •

edited

Loading

icyJoseph commented Sep 19, 2023 •

edited

Loading

Hardel-DW commented Sep 19, 2023 •

edited

Loading

FaryarKankash commented Sep 20, 2023 •

edited

Loading

cheryl-c-tirerack commented Sep 22, 2023 •

edited

Loading

cheryl-c-tirerack commented Sep 27, 2023 •

edited

Loading

cheryl-c-tirerack commented Sep 27, 2023 •

edited

Loading

Zanzofily commented Oct 6, 2023 •

edited

Loading

amiryxe commented Oct 6, 2023 •

edited

Loading