Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
All iPads I'm angry with Apple, and Disappointed (Safari reloading tabs)
- Thread starter NeoiPad
- Start date
- Sort by reaction score
On an air with iOS 7? Hard to believe. Why? Because all browsers on iOS are required to use WebKit and the apple web/java script engine. (Safari uses a special "faster" JavaScript engine that other browsers don't get access to.)
So in effect all browsers on iOS use the same rendering code. At least that's what I got out of the several articles I've read on the subject.
The one exception, if memory serves is Opera, and they get around this by rendering pages on a black-end proxy server (for iOS devices only) before sending them to your iOS device pre-rendered.
http://www.buzzfeed.com/jwherrman/the-problem-with-chrome-for-ios
By the way, I looked for some of those articles while writing this post, but I switched to chrome to do so, so that my draft post in Safari wouldn't reload on me. Chrome started reloading pages after only three tabs.
I've opened as many as 6 tabs going back and forth, opening and closing the app with not so much as a reload. The app did unexpectedly quit a couple of times.
Just replaced the iPad 4 with an Air and did some testing.
With 4 tabs opened and a couple of apps it has a little more than 200 Mb free.
So the 64-bit architecture is a little bit more memory leaking (by 80-85 Mb in the same condition).
But no reloads on Safari so far, like it was on my iPad 4.
With 4 tabs opened and a couple of apps it has a little more than 200 Mb free.
So the 64-bit architecture is a little bit more memory leaking (by 80-85 Mb in the same condition).
But no reloads on Safari so far, like it was on my iPad 4.
LOL - the good news was the operation was a success (6 tabs going back and forth) the bad news is the patient died (the app did quit unexpectedly a few times). Apps "quitting" means they crashed and burned. Not generally seen as a positive, or small inconvenience.
I don't know if it's RAM/64bit/iOS7 or what, but it's pretty clear that iPad web browsing is not anywhere as reliable/stable as it used to be.
As I've mentioned before I have an open ticket regarding this matter with a senior Apple support specialist. She told me today that Apple engineering is still collecting data on this issue and that if I knew other people with the same issue to have them call Apple support. I recommend for people to call Apple support request to speak to an senior support engineer and have them open a ticket with Apple engineering.
Probably not a bad idea to get apple involved. Why not? It costs you nothing and if they collect enough data then I bet it gets some attention. I thought I read though that 7.2 beta might take care of some of this?
Apple engineering hasn't a clue how to fix this. There's a 16 page thread on Apple's support forum that started in Mid November in regards to this.
They say the same thing, call a specialist, collecting data, speak to a senior support engineer.
I guarantee if anybody were to call them right now they'd tell you this is the 1st they've heard of it. After they have you do a software restore, (which won't fix it) they'll have you return/exchange it.
Software isn't going to fix a hardware, (lack of) problem.
Last edited:
Really no clue??? Sorry pal it's already confirmed to be much much better in the 7.1 beta 2.
It doesn't hurt to try.
They have dozens of senior engineers, they are not likely to know about every single case. That's why you're supposed to call them in the first place, help them collect the data, so they can log it into the system and one of the managers will prioritize it to the right team.
I've filed many radars in the past, Apple did eventually resolved majority of them over time. They just need data to figure out what the problem is.
As jonny just said, it's already confirmed to be hugely improved in iOS 7.1 beta 2.
----------
Did she give you any case numbers that we can use?
----------
Until it is resolved, you should go ahead and send the data in. If they confirm it is fixed, then they'll just close your case. It doesn't hurt them to have another test to make sure what they did is enough.
What constitutes fixed to you? Tabs are gonna reload eventually and 64 bit apps require more RAM. Someone already posted a video of the beta with a ton of tabs open. Right now most people can keep at least 2 or 3 tabs open no problem during typical use. If the beta at least doubles that, then I don't see the issue.
If you really need a crap load of tabs open ( most people don't), then get a laptop and quit whining.
It doesn't give them all the data they need, it just tells them an area to start but it doesn't tell them how it crashed exactly. It's up to us to tell them how to reproduce it.
If you're a developer, you should be sending those data in as radars, not leave it to Apple to figure it out on their own.
I'm using the air since yesterday, with usually 3 tabs opened and a couple of apps in background without any issue ....
So in the very unlikely event it isn't fixed this hardware generation I'm now covered because I have an open support ticket with Apple documenting the issue and my support ticket falls within the return period. I've worked for several hardware vendors in the past including Dell and Gateway and I can tell you this will buy you a lot leeway later on.
If you wait until your return period ends or never open up a support case than you'll won't have a leg to stand on.
I'll ping the support tech on it. I have a support case # for myself but I'll see if they have a general case number people can use.
Ditto, thats my situation. Everyone here makes it sound like its the end of the world not being able to have more than 3 or 4 tabs open. Thats all most people need. I get that theres definitely a memory leak problem but in a couple weeks time....maybe even today. That wont be a problem.
Maybe it's just me, but this is a tablet, not a personal computer.
I don't trust the all-in-one solutions.
My iPad is just PERFECT for 90% of my daily needs, but when I need a proper computer, I do have a MBP with a decent display estate, a real keyboard and enough ram to open 10 or 20 tabs if needed.
Last edited:
Thats exactly what Apple has always gone for. Whats best for 90% of the people 90% of the time. I'm not saying this isn't an issue, just not as big as people are making it.
Well, just multiply the size of the original page by, say, 40. Then, you get the approximate RAM usage of Safari after loading the page.
Of course, that 40 isn't a precise figure. With one of the test pages I've been testing UIWebView / Safari's memory usage, http://winmobiletech.com/a/1.html , is 595kbyte , while it takes Safari exactly 22 Mbyte to render it on an iPad 3 running on all the tested iOS versions (6.1.2, 7.0.4, 7.1b2).
With a Web page with far more / larger inline images / videos, the figure is way larger. For example, the HTML page of http://nin.com (another page I've run tests with) is 100 kbytes only, but, on the same iPad 3, it occupies 330...390 Mbytes under all the above-listed iOS versions because of the huge number of hi-res inline images / videos. That is, the multiplier with this page is about a whopping 3600.
The above numbers are "static" and only show the memory occupied after loading. If you start scrolling the page, the memory usage can, in cases, dramatically increase; particularly if you scroll down to the bottom and, then, tap the status bar to quickly scroll up to the top. If casual scrolling doesn't crash your Safari, the latter may as it uses the most memory.
100% true. I called apple support so many times. Also claimed it was first they'd heard of it. Did all sorts of tests and they could identify a low memory issue.
Eventually decided to take it in store. Was given a new ipad air. Out the box it was 7.0.3. I decided not to update yet.
Worked fine for couple of days - and then problems start all over again
Who knows what's going on?
One of two things is going on.
Some RAM in your iPad magically disappeared after a couple of days.
Or.
There is a software bug.
Take your pick.
The problem is ..... YOU.
Are you closing unused apps in background ? Are you closing unused tabs in the browser ?
Right now I have two tabs opened, the Mail, iPhoto and iTranslate in background and my iPad is working very well.
What did you do to cause the issue ?
Last time I checked my iPad air and my iPad 4 were running iOS 7 and since I don't have the problem .... iOS isn't the problem.