-
Notifications
You must be signed in to change notification settings - Fork 1.9k
[iOS] Fix memory leak in CarouselViewHandler2 #29719
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
Conversation
|
Hey there @@bhavanesh2001! Thank you so much for your PR! Someone from the team will get assigned to your PR shortly and we'll get it reviewed. |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
The CarouselView tests failed on CI due to the changes introduced by this PR. Setting the FlowDirection to either LeftToRight or RightToLeft on CarouselView is now failing. |
|
@sheiksyedm Thanks for letting me know. #29784 should fix the failures |
Note
Are you waiting for the changes in this PR to be merged?
It would be very helpful if you could test the resulting artifacts from this PR and let us know in a comment if this change resolves your issue. Thank you!
Description of Change
CarouselViewHandler2sets aVisibleItemsInvalidationHandleron theNSCollectionLayoutSectionduring layout construction. This handler captures strong references toVirtualViewandController, causing a memory leak.Updated the handler to use WeakReference's. Moved Layout creation to
LayoutFacotryIssues Fixed
Fixes #29677