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
Grateful for such a great control, I am in the process of using each Liked or Nope will have a memory leak. May I ask how to deal with memory leaks?
Content from GOOGLE translation problem.
The text was updated successfully, but these errors were encountered:
Yeah, there definitely is a memory leak here. Received this email from (I think?) @stevem21m:
I've been using your sample code MDCSwipeToChoose.
In the sample ChoosePersonView, I'm setting the image view image with AFNetworking setImageWithURL. Anyhow, the Virtual memory for CG raster data grows and grows and eventually crashes. Any thoughts on how to deallocate the images from being allocated to virtual memory. I've been banging my head on this all day and can't find any solution online. At first I thought it might the the way AFNetworking caches the images, but it's not, it's like all the images are being held hostage by memory.
I just profiled the sample app. I'm not sure I see any leaks. Are you sure your problem wasn't fixed in pull request #4? If you still have a problem on the latest version (0.2.1), please open another issue.
Grateful for such a great control, I am in the process of using each Liked or Nope will have a memory leak. May I ask how to deal with memory leaks?
Content from GOOGLE translation problem.
The text was updated successfully, but these errors were encountered: