Document signal retention behavior of AbortSignal.any() - #45353
Open
1t1sCooL wants to merge 1 commit into
Open
Conversation
sideshowbarker
removed their request for review
September 1, 2026 11:33
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Adds a Description section to the
AbortSignal.any()reference page documenting that the returned signal stays linked to (and retained by) the input signals until one of them aborts or all become unreachable, with a minimal example of the problematic pattern (repeatedly combining a long-lived signal with short-lived ones) and how to avoid it (abort the short-lived controller when its operation completes).Motivation
Fixes #44695 — the scope follows the discussion in that issue: focused on
AbortSignal.any()only, per the reporter's suggested note and the maintainer's confirmation that the addition is reasonable.