This post is part 4 of series of Xamarin.Forms – real life stories posts.
The nature of the application we were creating is that it is in use almost 24×7. And memory leaks, even small ones, pile up. And at some stage iOS throws you a memory warning, and shortly afterwards, application gets killed. First time we noticed the problem was when the application was about 50% ready and serious testing started. Our tester complained that after 2 hours of use, the application became slow and then it crashes. Investigation of crash files with native iOS tools showed that operating system killed the app because of excessive memory use.
Now we know the exact cause of the problem, how do we solve it?