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
After inspecting in memory objects of this package in XCODE , I noticed ACR doesn't pick it should release NativeVideoPlayerAPI.
Adding screen shots of my app's analysis showing me switching between pages with NativeVideoPlayer to ones without, but NativeVideoPlayerAPI is not de-initing
I took this screen shot after I switched to page, after scrolling some 60 videos.
Then I came back to the videos page (you can see only 7 are rendered at the same time
and again to page without the videos, you can see almost everything got disposed but not the API.
those objects keep stacking up until I get oom after scrolling enough videos.
this problem is worse in V3 since all objects there are not de-initing (controller, view, etc ...)
you can use this guide to replicate this leak
The text was updated successfully, but these errors were encountered:
@VerioN1 thank you for reporting this issue. I've just published v 3.0.0-dev.4 with some potential fixes. would you mind testing it out and see if you still see the same issue or not? thanks
After inspecting in memory objects of this package in XCODE , I noticed ACR doesn't pick it should release NativeVideoPlayerAPI.
Adding screen shots of my app's analysis showing me switching between pages with NativeVideoPlayer to ones without, but NativeVideoPlayerAPI is not de-initing
I took this screen shot after I switched to page, after scrolling some 60 videos.
Then I came back to the videos page (you can see only 7 are rendered at the same time
and again to page without the videos, you can see almost everything got disposed but not the API.
those objects keep stacking up until I get oom after scrolling enough videos.
this problem is worse in V3 since all objects there are not de-initing (controller, view, etc ...)
you can use this guide to replicate this leak
The text was updated successfully, but these errors were encountered: