Title: Uncatchable exception from webstream adapter · Issue #64120 · nodejs/node · GitHub
Open Graph Title: Uncatchable exception from webstream adapter · Issue #64120 · nodejs/node
X Title: Uncatchable exception from webstream adapter · Issue #64120 · nodejs/node
Description: Version v26.3.1 Platform Microsoft Windows NT 10.0.19045.0 x64 Subsystem No response What steps will reproduce the bug? The following code reproduces the bug: import { connect, createServer } from "net"; import { Duplex } from "stream"; ...
Open Graph Description: Version v26.3.1 Platform Microsoft Windows NT 10.0.19045.0 x64 Subsystem No response What steps will reproduce the bug? The following code reproduces the bug: import { connect, createServer } from ...
X Description: Version v26.3.1 Platform Microsoft Windows NT 10.0.19045.0 x64 Subsystem No response What steps will reproduce the bug? The following code reproduces the bug: import { connect, createServer } from ...
Opengraph URL: https://github.com/nodejs/node/issues/64120
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Uncatchable exception from webstream adapter","articleBody":"### Version\n\nv26.3.1\n\n### Platform\n\n```text\nMicrosoft Windows NT 10.0.19045.0 x64\n```\n\n### Subsystem\n\n_No response_\n\n### What steps will reproduce the bug?\n\nThe following code reproduces the bug:\n```typescript\nimport { connect, createServer } from \"net\";\nimport { Duplex } from \"stream\";\n\nconst server = createServer();\n\nserver.on(\"connection\", (socket) => {\n socket.end();\n});\n\nserver.listen(8444, () => {\n console.log(\"server listening on port 8444\");\n});\n\nconst socket = connect({ host: \"localhost\", port: 8444 });\nconst conn = Duplex.toWeb(socket);\n\nconst reader = conn.readable.getReader();\nconst writer = conn.writable.getWriter();\n\ntry {\n await reader.read();\n await writer.close();\n} catch {}\n```\n\n\n\n### How often does it reproduce? Is there a required condition?\n\nHappens consistently on Node 26.3.0 and 26.3.1\nDoesn't happen on Node 26.2.0\n\n### What is the expected behavior? Why is that the expected behavior?\n\nIt should not produce an uncatchable exception.\n\n### What do you see instead?\n\nNode will exit with the uncaught exception:\n```\nnode:internal/webstreams/adapters:224\n controller.error(new AbortError());\n ^\n\nTypeError: Cannot read properties of undefined (reading 'error')\n at Socket.\u003canonymous> (node:internal/webstreams/adapters:224:16)\n at Socket.\u003canonymous> (node:internal/util:581:20)\n at Socket.onfinish (node:internal/streams/end-of-stream:238:16)\n at Socket.emit (node:events:509:20)\n at finish (node:internal/streams/writable:955:10)\n at process.processTicksAndRejections (node:internal/process/task_queues:90:21)\n```\n\n### Additional information\n\n_No response_","author":{"url":"https://github.com/basro","@type":"Person","name":"basro"},"datePublished":"2026-06-24T22:32:46Z","url":"https://github.com/nodejs/node/issues/64120"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react-reconciler,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@d5750093facf |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:b6ce4928-ba38-7086-4a16-852299d757e9 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | C468:125BB0:790223:9CE844:6AED317D |
| html-safe-nonce | 8a9151af61e5c732f0d3a04715d2dbdd69ac8faadc5238146f73a344625da345 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJDNDY4OjEyNUJCMDo3OTAyMjM6OUNFODQ0OjZBRUQzMTdEIiwidmlzaXRvcl9pZCI6IjMzMDE2ODI0OTkxNDk0NDM0NTMiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | 7ea1b3c39bb3579e8794ec2dd466aa0b0c5beec9799c189601e4375f1b5c2a51 |
| hovercard-subject-tag | issue:4738964779 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/nodejs/node/64120/issue_layout |
| twitter:image | https://opengraph.githubassets.com/08bfbae66a9b0949760bd375dd27fba7d37c55ca83013756084f6e226a91c045/nodejs/node/issues/64120 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/08bfbae66a9b0949760bd375dd27fba7d37c55ca83013756084f6e226a91c045/nodejs/node/issues/64120 |
| og:image:alt | Version v26.3.1 Platform Microsoft Windows NT 10.0.19045.0 x64 Subsystem No response What steps will reproduce the bug? The following code reproduces the bug: import { connect, createServer } from ... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | basro |
| hostname | github.com |
| expected-hostname | github.com |
| None | e51d0b7b5ab34b1688c05b54c3ed17b8658b2fa9bca973a9c740683ccb12cf4a |
| turbo-cache-control | no-preview |
| go-import | github.com/nodejs/node git https://github.com/nodejs/node.git |
| octolytics-dimension-user_id | 9950313 |
| octolytics-dimension-user_login | nodejs |
| octolytics-dimension-repository_id | 27193779 |
| octolytics-dimension-repository_nwo | nodejs/node |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 27193779 |
| octolytics-dimension-repository_network_root_nwo | nodejs/node |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 59ebb7b901cc154ecc179a44f266fcf69f343b30 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width