Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(cdk/scrolling): unsubscribe from scrolled stream when viewport is destroyed #27800

Merged
merged 1 commit into from
Sep 18, 2023

Conversation

crisbeto
Copy link
Member

Initially the virtual scroll viewport was written under the assumption that it is the scrollable and that it doesn't need to unsubscribe from its elementScrolled stream, because it'll be completed on destroy. This might not be the case if a CdkVirtualScrollableElement is provided and the viewport might be destroyed without the scrollable being destroyed.

These changes add a takeUntil to avoid any potential leaks.

Fixes #27799.

… destroyed

Initially the virtual scroll viewport was written under the assumption that it is the scrollable and that it doesn't need to unsubscribe from its `elementScrolled` stream, because it'll be completed on destroy. This might not be the case if a `CdkVirtualScrollableElement` is provided and the viewport might be destroyed without the scrollable being destroyed.

These changes add a `takeUntil` to avoid any potential leaks.

Fixes angular#27799.
@crisbeto crisbeto added P4 A relatively minor issue that is not relevant to core functions target: patch This PR is targeted for the next patch release labels Sep 18, 2023
@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Sep 18, 2023
@crisbeto crisbeto merged commit 31187ab into angular:main Sep 18, 2023
crisbeto added a commit that referenced this pull request Sep 18, 2023
… destroyed (#27800)

Initially the virtual scroll viewport was written under the assumption that it is the scrollable and that it doesn't need to unsubscribe from its `elementScrolled` stream, because it'll be completed on destroy. This might not be the case if a `CdkVirtualScrollableElement` is provided and the viewport might be destroyed without the scrollable being destroyed.

These changes add a `takeUntil` to avoid any potential leaks.

Fixes #27799.

(cherry picked from commit 31187ab)
@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 Oct 19, 2023
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 P4 A relatively minor issue that is not relevant to core functions target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

bug(CdkVirtualScrollViewport): no unsubscribe from scrolling after destroy
2 participants