Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Animations (switching between viewControllers, scrolling tableView) on device are working with spurts but on simulator work fine. How to solve this problem?
I’m afraid there is no easy answer.
The only solution is to improve your code and make it lighter and more efficient.
I ran into such problems too and I had no other option but to make my module work better.
The first suggestion would be to check for memory leaks (this one helped me: http://www.friday.com/bbum/2010/10/17/when-is-a-leak-not-a-leak-using-heapshot-analysis-to-find-undesirable-memory-growth/ ). Fixing the leaks should give a little more memory to work with.
If you have this spurts on the first gen ipad… meh, it’s so and so. but if you have them on the ipad2, then you really need to rewrite your code: use less elements, make less operations, maybe use some background operations to perform some threads so you can leave the main thread free to make the animations