Skip to content

Conversation

@arturovt
Copy link
Contributor

@arturovt arturovt commented Jun 4, 2025

We should remove the onDestroy listener once subscription is unsubscribed because components might not be destroyed yet, but they still would capture subscribers.

We should remove the `onDestroy` listener once subscription is unsubscribed because components might not be destroyed yet, but they still would capture subscribers.
@pullapprove pullapprove bot requested a review from crisbeto June 4, 2025 21:14
@angular-robot angular-robot bot added the area: core Issues related to the framework runtime label Jun 4, 2025
@ngbot ngbot bot added this to the Backlog milestone Jun 4, 2025
@thePunderWoman thePunderWoman removed the request for review from crisbeto June 5, 2025 06:10
@thePunderWoman thePunderWoman added action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note labels Jun 5, 2025
@thePunderWoman
Copy link
Contributor

Caretaker note: this is safe to merge. the failing G3 test is a flake.

@pkozlowski-opensource
Copy link
Member

This PR was merged into the repository by commit e81ea0c.

The changes were merged into the following branches: main, 20.0.x

pkozlowski-opensource pushed a commit that referenced this pull request Jun 5, 2025
We should remove the `onDestroy` listener once subscription is unsubscribed because components might not be destroyed yet, but they still would capture subscribers.

PR Close #61882
@arturovt arturovt deleted the fix/core-outputToObservable-unregister branch June 5, 2025 10:33
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jul 6, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker area: core Issues related to the framework runtime merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants