You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MaxListenersExceededWarning: Possible EventTarget memory leak detected. 11 abort listeners added to [AbortSignal]. Use events.setMaxListeners() to increase limit
A cursory read of the code suggests that listeners added via deriveAbortController are not properly cleaned up in the case that the signal is not aborted (and there seems to be no mechanism by which these hanging listeners might be removed).
I also note that toPromise offers no mechanism have its listeners removed in the case that the signal doesn't abort. This isn't covered by the PR above, but would be caught by the following test:
Repro in nodejs (with TS support via tsx):
After about 11 retries, in the output, we see:
A cursory read of the code suggests that listeners added via
deriveAbortController
are not properly cleaned up in the case that the signal is not aborted (and there seems to be no mechanism by which these hanging listeners might be removed).Here is a reproduction, running in StackBlitz (apparently only working in chromium-based browser for me 🤨 ).
The text was updated successfully, but these errors were encountered: