-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
memory leak in fetch() #51438
Comments
Maybe transfer the issue in undici? |
Think so? cc @KhafraDev |
Does that reproduce on undici main? |
Yeah, I can confirm that |
You want me to re-file it in the other repo? |
After a bit more inspection it seems that the memory does indeed go down after a few seconds, but it never goes down to what it was before the fetches. In other words, if you run the same one-liner above multiple times, and wait a number of seconds in between runs.
But it seems to be fixed in
|
(from undici main)
|
So this seems already fixed in main (it has the latest undici landed). |
Hmm, I might be reproduce wrongly the. Sorry for the wrong callout |
Version
v19.9.0
Platform
Linux www 5.10.0-26-amd64 #1 SMP Debian 5.10.197-1 (2023-09-29) x86_64 GNU/Linux
Subsystem
fetch/undici
What steps will reproduce the bug?
Simply run this code and watch the memory usage increase without decreasing. The code itself shouldn't hold references to anything.
How often does it reproduce? Is there a required condition?
Every time
What is the expected behavior? Why is that the expected behavior?
Memory usage should stay at the same value after a
fetch()
call, because there are no references to it.What do you see instead?
Memory usage increasing:
Additional information
Discussion started in #51429 which seems to be similar or a duplicate of #46435.
The text was updated successfully, but these errors were encountered: