-
Notifications
You must be signed in to change notification settings - Fork 91
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
Memory Issue #42
Comments
The data is stored in There may be memory leaks causing the issues you're describing. I would add deinits to If you find there's a bug in the implementation, please report it |
I tried it but can not achieved this. Can you give example to add &c call deinits to ResourceLoaderDelegate and CachingPlayerItem. |
I also want to remove the cached items. Please help |
There's no caching done by CachingPlayerItem. It only gives you the raw Data via a delegate, and it's up to you how to cache it (and how to delete it from your cache). |
Hi, so I'm working in SwiftUI. I added prints to the existing CachingPlayerItem class and then the contained class ResourceLoaderDelegate. In my case it looks like the CachingPlayerItem deinit is fired every second--is this the correct behavior? For every deinit CachingPlayerItem that is fired, there is a ResourceLoaderDelegate deinit that is fired as well. I'm getting a Memory error in the processPendingRequests() function when it tries to map the pending requests. Not sure why exactly this error would be happening. All I've done is replaced all my existing AVPlayer(url:) structs with AVPlayer(playerItem:) structs instead. Should the cache be working in this situation? Not sure how to continue debugging because I don't understand the module 100%. Any help is much appreciated! |
After a certain number of videos have been downloaded, the application is terminated by memory error. For this, can we save the downloaded data to disk instead of memory?
If we can't do this, can you help us how to remove the downloaded data from memory? (I know that the data is not cached, but as long as the application is open, the downloaded data is kept in memory, causing memory issue)
The text was updated successfully, but these errors were encountered: