MaxListenersExceededWarning: Possible EventTarget memory leak detected. 101 abort listeners added to [AbortSignal]Β #47449
Copy link
Copy link
Closed
Description
Activity
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
cc @KhafraDevReacted by Khafra and Fawaz AhmedThis warning message still seems to be there in
v19.9.0Reacted by AmirStill occurring in v21.6.1 . Was there a regression?
Yes, this bug still exists
Not fixed. Node.js v20.11.0.
"undici": "^6.7.1"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); }
(node:18748) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 101 abort listeners added to [AbortSignal]. Use events.setMaxListeners() to increase limit (Use `node --trace-warnings ...` to show where the warning was created) (node:18748) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 102 abort listeners added to [AbortSignal]. Use events.setMaxListeners() to increase limit (node:18748) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 103 abort listeners added to [AbortSignal]. Use events.setMaxListeners() to increase limit (node:18748) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 104 abort listeners added to [AbortSignal]. Use events.setMaxListeners() to increase limit (node:18748) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 105 abort listeners added to [AbortSignal]. Use events.setMaxListeners() to increase limit (node:18748) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 106 abort listeners added to [AbortSignal]. Use events.setMaxListeners() to increase limit (node:18748) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 107 abort listeners added to [AbortSignal]. Use events.setMaxListeners() to increase limit (node:18748) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 108 abort listeners added to [AbortSignal]. Use events.setMaxListeners() to increase limit (node:18748) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 109 abort listeners added to [AbortSignal]. Use events.setMaxListeners() to increase limit (node:18748) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 110 abort listeners added to [AbortSignal]. Use events.setMaxListeners() to increase limit- added a commit that references this issue
on Jun 25, 2024
Metadata
Metadata
Assignees
Labels
No labels
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
MaxListenersExceededWarningis shown in v19.8.1, it did not appear in v19.5What is the expected behavior? Why is that the expected behavior?
The
MaxListenersExceededWarningshould not appear assetMaxListenersis already set toInfinityin the code aboveWhat do you see instead?
Additional information
No response