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
MaxListenersExceededWarning: Possible EventTarget memory leak detected. 101 abort listeners added to [AbortSignal] #47449
Comments
Related nodejs/undici#1910 |
I think this would be solved once #47039 lands on a release line, undici can then set the max value to the value of max event listeners of the given signal I believe |
This warning message still seems to be there in |
Still occurring in v21.6.1 . Was there a regression? |
Yes, this bug still exists |
Not fixed. Node.js v20.11.0. abort_test.mjs import { setMaxListeners } from "node:events";
import { fetch } from "undici";
const { signal } = new AbortController();
setMaxListeners(110, signal);
for (let i = 0; i < 110; i += 1) {
fetch("https://1.1.1.1/cdn-cgi/trace", { signal }).catch(console.error);
}
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
v19.8.1
Platform
Microsoft Windows NT 10.0.22000.0 x64
Subsystem
No response
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
This
MaxListenersExceededWarning
is shown in v19.8.1, it did not appear in v19.5What is the expected behavior? Why is that the expected behavior?
The
MaxListenersExceededWarning
should not appear assetMaxListeners
is already set toInfinity
in the code aboveWhat do you see instead?
Additional information
No response
The text was updated successfully, but these errors were encountered: