Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fetch is sometimes crashing entire node process since upgrading from node 22.9.0 to 23.1.0 #3813

Open
KMatuszak opened this issue Nov 8, 2024 · 3 comments

Comments

@KMatuszak
Copy link

Bug Description

fetch is sometimes crashing entire node process since upgrading from node 22.9.0 to 23.1.0

Logs & Screenshots

node:events:485
      throw er; // Unhandled 'error' event
      ^

TypeError: terminated
    at Fetch.onAborted (node:internal/deps/undici/undici:11020:53)
    at Fetch.emit (node:events:507:28)
    at Fetch.terminate (node:internal/deps/undici/undici:10178:14)
    at Object.onError (node:internal/deps/undici/undici:11141:38)
    at Request.onError (node:internal/deps/undici/undici:2094:31)
    at Object.errorRequest (node:internal/deps/undici/undici:1591:17)
    at TLSSocket.<anonymous> (node:internal/deps/undici/undici:6263:16)
    at TLSSocket.emit (node:events:519:35)
    at node:net:350:12
    at TCP.done (node:_tls_wrap:650:7)
Emitted 'error' event on Readable instance at:
    at emitErrorNT (node:internal/streams/destroy:170:8)
    at emitErrorCloseNT (node:internal/streams/destroy:129:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
  [cause]: Error: read ECONNRESET
      at TLSWrap.onStreamRead (node:internal/stream_base_commons:216:20) {
    errno: -104,
    code: 'ECONNRESET',
    syscall: 'read'
  }
}

Environment

amd64 node:23.1.0-bookworm docker image

@KMatuszak KMatuszak added the bug Something isn't working label Nov 8, 2024
@mcollina
Copy link
Member

mcollina commented Nov 8, 2024

Thanks for reporting!

Can you provide steps to reproduce? We often need a reproducible example, e.g. some code that allows someone else to recreate your problem by just copying and pasting it. If it involves more than a couple of different file, create a new repository on GitHub and add a link to that.

@KMatuszak
Copy link
Author

Unfortunately I don't think it's possible to create this, and I know that this report probably doesn't help much without it. It happens randomly about once a day when doing various simple fetches.

@koplenov
Copy link

koplenov commented Nov 8, 2024

+1

@mcollina mcollina added missing minimal reproduction and removed bug Something isn't working labels Nov 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants