-
Notifications
You must be signed in to change notification settings - Fork 935
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
App crashing due to memory pressure #79
Comments
How are you calling |
I am calling inside tableview's cell API. When image is returned by completion block, it is set to cell's avatar image view. No the table is backed by NSFetchedResultsController. |
Pretty sure any memory pressure is being caused either by the way you are decoding and drawing images or by a leak in your app code. Either way, it's unlikely that FIC is the culprit. If you provide an instruments trace, I could take a look. Closing until there's actionable info... |
Currently, I am not working on that, if possible, I can check and give you more info. Thanks for the reply. |
Hi,
When I use the Fast image cache for loading images in a table view, after scrolling for some time the app crashes dud to memory pressure. I thought the main culprit might be my model object (core data) which might be taking too much memory when called from tableview's cell API.
[FICImageCache sharedImageCache] asynchronouslyRetrieveImageForEntity:imageEntity withFormatName:ImageAvatarFormatFriendsList completionBlock:^(id entity, NSString *formatName, UIImage *image)
and I created a small model object called ImageEntity which contains necessary attributes like object ID and image path to respect the FICEntity protocol.
Even though having this small model objects app crashes when I do scrolling in the table view.
Here are the some more points to analyse this issue.
Any idea why it is taking too much memory?
Any help is highly appreciated.
Thanks.
The text was updated successfully, but these errors were encountered: