Question

I've got a question, my app consists of several CollectionViews next to each other in a ScrollView, if one Cell gets clicked, a Detail view appears, using this code:

DetailCell *detailCell = [[DetailCell alloc] initWithDetails:_pageCategorie and: indexPath];
[_nav pushViewController:detailCell animated:YES];

Everything works flawlessly, you can go to the DetailView, then back to CollectionView and then on the DetailView of another Cell, and so on... The Problem is, that if you repeat this several times (10+) the app starts to heavily lag on my iPhone. So I think when I leave a DetailView and get back to the CollectionView, the DetailView remains in the memory. What can I do against this behavior? I'm using ARC if it does matter

No correct solution

OTHER TIPS

Xcode's memory tool can be tricky. Depending on how it is configured it might be reporting allocated objects, instead of objects in use. This means that even if your objects get deallocated, the memory tool might report otherwise.

Check this link to see how you can modify the configuration of memory report in XCode.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top