You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 17, 2023. It is now read-only.
I using ScalePageView to show 10 different video that are bundled in the app. In profiling the app with the Xcode Leak Instrument, I see leaks related to PagingCollectionViewController.update and .collectionView.
In the Leak tool, when I double click on the cellForItemAt I get the cell.update....and I see that parent captures self. I'm wondering if this causes a leak when the cell gets dequeued or for some other reason? It could be my implementation that is some how causing this. I did run your sample app in the Leak tool and the same leak does not occur.
Would you have any suggestions and how I can further debug or eliminate this leak?
Thanks,
Dave
The text was updated successfully, but these errors were encountered:
Hi, thanking for reporting the issue, I can tell the line you mentioned cell.update(value: list[indexPath.row], index: indexPath, parent: self) doesn't cause any memory leak since it's not async, but there might be another cause.
Could you send a simple project that reproduces the memory leak issue? I can use that to investigate the problem
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
I using ScalePageView to show 10 different video that are bundled in the app. In profiling the app with the Xcode Leak Instrument, I see leaks related to PagingCollectionViewController.update and .collectionView.
In the Leak tool, when I double click on the cellForItemAt I get the cell.update....and I see that parent captures self. I'm wondering if this causes a leak when the cell gets dequeued or for some other reason? It could be my implementation that is some how causing this. I did run your sample app in the Leak tool and the same leak does not occur.
Would you have any suggestions and how I can further debug or eliminate this leak?
Thanks,
Dave
The text was updated successfully, but these errors were encountered: