bug(queue): AsyncQueue leaks pending resolvers on abandoned iteration #34984

Activity

1. github-actions

   assigned

   jlongster

   on Jul 2, 2026
2. github-actions commented on Jul 2, 2026

   

   github-actionsBot

   on Jul 2, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues related to AsyncQueue and memory leaks. Please check:

   • Memory leak: SSE connections stuck in CLOSE_WAIT cause unbounded AsyncQueue growth (~14 MB/sec) #22198: Memory leak specifically caused by unbounded AsyncQueue growth when SSE consumers stop draining — directly related to AsyncQueue not cleaning up when iteration is abandoned
   • SSE event subscriptions buffer without bound when the consumer stops draining #31923: SSE event subscriptions buffer without bound when the consumer stops draining — same root cause in the queue abstraction
   • Memory Megathread #20695: Memory megathread tracking multiple related memory leak reports

   If your issue describes a distinct scenario (e.g., a for await...of consumer breaking early rather than SSE-specific stalls), it may still be worth keeping open as a separate code path. But please review the above to see if they cover your case.
3. HEETMEHTA18 commented on Jul 2, 2026

   

   HEETMEHTA18

   on Jul 2, 2026

   Author

   More actions

   This covers a distinct scenario from the SSE memory leaks (#22198, #31923). Those are about server-side zombie TCP connections where the server never detects client disconnect — the fix there belongs in the SSE/connection layer.

   This issue is about the general-purpose AsyncQueue having no way to clean up pending resolvers when a consumer deliberately abandons iteration (e.g. break/return from for await...of). The fix is adding a close() method so any consumer can terminate the queue cleanly.

   The two issues share the same utility class but have different root causes and different fix locations. This one is a prerequisite for any queue-level cleanup regardless of the SSE story.
4. github-actions commented on Sep 1, 2026

   

   github-actionsBot

   on Sep 1, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
5. github-actions

   closed this as not plannedon Sep 1, 2026