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.

Sign up for GitHub

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

Jump to bottom

AbortController/AbortSignal memory leak #3647

Open
System233 opened this issue Sep 26, 2024 · 2 comments
Open

AbortController/AbortSignal memory leak #3647

System233 opened this issue Sep 26, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@System233
Copy link

Bug Description

The memory of the Node process grows infinitely, ultimately resulting in an OOM error. Memory profiling revealed a memory leak related to AbortController.

I am using fetch API with AbortController/AbortSignal in Node.js(not undici directly).

Reproducible By

Expected Behavior

AbortController should be destroyed along with fetch.

Logs & Screenshots

image
image

Environment

Node: v22.3.0
Docker Image: node:apline

Additional context
@System233 System233 added the bug Something isn't working label Sep 26, 2024
@ronag
Copy link
Member

ronag commented Sep 26, 2024

Can you try with node 22.9? I believe this was fixed quite recently.

@mcollina
Copy link
Member

Can you please include a reproduction?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mcollina @ronag @System233