I’m working on an ipad app which is meant to have several UIWebView controls visible at once, and was wondering what a sensible limit is to the number that we can have before running into memory issues on the ipad?
Thanks
Share
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.
I’m working on an ipad app which is meant to have several UIWebView controls visible at once, and was wondering what a sensible limit is to the number that we can have before running into memory issues on the ipad?
Thanks
You have to be dynamic about it. Don’t set a hard limit in your app, wait for the memory warning and then start purging web views, lazily reloading them as the user needs them. You should screenshot the view first using
[CALayer renderInContext:]so it appears seamless.After all each web view will have different memory and CPU requirements. As always, the mantra is test, test, test.
… but, of course, Safari limits you to nine open tabs. Which is very much a hard limit. So… there’s that.