lib: disable default memory leak warning for AbortSignal#55816
Merged
nodejs-github-bot merged 1 commit intonodejs:mainfrom Dec 7, 2024
Merged
lib: disable default memory leak warning for AbortSignal#55816nodejs-github-bot merged 1 commit intonodejs:mainfrom
nodejs-github-bot merged 1 commit intonodejs:mainfrom
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This change sets the default
kMaxEventTargetListenersproperty forAbortSignalinstances to 0, disabling the check per default, to enable users to write isomorphic library code.If desirable, the max event target listeners check can still be enabled for individual
AbortSignalinstances by callingsetMaxListenerson them.Refs: #54758
I ran all the test I believe are relevant locally, but I can't run the full test suite as I'm working on a managed Mac and can't change firewall rules, so the test suite just explodes on me with popups.