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.
Safari tab reloading is FIXED in 7.1 beta 3
- Thread starter zunairryk
- Start date
- Sort by reaction score
Ok, I did what you suggested after I updated to 7.1. and Safari crashed after double tapping a few times. Now I have to decide if I am keeping the Air. I still have my 1st gen Mini. I need to check on tabs reloading as well.
Where are you Count?
Ok, I did what you suggested after I updated to 7.1. and Safari crashed after double tapping a few times. Now I have to decide if I am keeping the Air. I still have my 1st gen Mini. I need to check on tabs reloading as well.
Where are you Count?
I just got home, installed 7.1 on the iPad, and am going to sleep. Work is apparently taking me away from testing this out for a couple days. I couldn't get the iphone5s page on apple.com to blow up safari after 30 seconds of zooming, double clicking and scrolling.
Sorry to disappoint, hopefully in a couple days.
Good luck all, hope it works out for you.
Ok, I did what you suggested after I updated to 7.1. and Safari crashed after double tapping a few times. Now I have to decide if I am keeping the Air. I still have my 1st gen Mini. I need to check on tabs reloading as well.
Where are you Count?
Exchange or return the air.
Not yet!
Clearing history and cache has that iphone 5s features page not crashing Safari.
Long way to go but for now I am past that hurdle at least for tonight.
Not yet!
Clearing history and cache has that iphone 5s features page not crashing Safari.
Long way to go but for now I am past that hurdle at least for tonight.
Clearing my cache didn't work for me. But powering the device down and restarting it did; the page no longer crashes for me. Guess I should have remembered that old Dilbert cartoon:
Last edited:
Just going to go through my normal routines using my Air on 7.1 from now on. I'm not going to go looking for problems and try to make Safari crash. I wasn't having any issues until I started to read posts where people gave examples of how to crash Safari. That isn't within my daily routine, scroll here, double tap there, use portrait, shake, rattle, and roll it, etc. etc. What I do is what I do, I never went on nin.com ever until recently when reading crashing examples.
If the Air works for what I do then fine I keep it. If not, I'll just return it.
That's really the best way to handle this issue. I also haven't had a problem with my Air at all, even with most of the tests people had me try here. Like you said, I use my device how I use it. I'm not a big multi tab user. I don't visit nin.com. So, for me everything is working fine.
I almost feel guilty..... Just got lucky, I guess.
That's really the best way to handle this issue. I also haven't had a problem with my Air at all, even with most of the tests people had me try here. Like you said, I use my device how I use it. I'm not a big multi tab user. I don't visit nin.com. So, for me everything is working fine.
I almost feel guilty..... Just got lucky, I guess.
I certainly don't understand folks getting lots of crashes.
I don't think refreshes have stopped but I don't open lots of tabs myself so I should be OK with that since I was before 7.1 anyway.
Here's hoping 7.1 fixes crashes for people or at least minimizes what they previously encountered. I see no reason why if anyone is dissatisfied why they cannot bring it to Apple since 7.1 was released if the problems continue with crashing. Tab reloads may definitely be an entirely different story but I'm not going to be looking for trouble any longer with that either.
Nin.com? What's that?
I was having frequent crashes before I read this thread; having a web-site where the problem is predictably reproducible just gives me a place to test it.
That said, my primary use for the iPad is reading, not web browsing, and that's working just fine. So even if they don't fix it it will be annoying, but I'll keep the device; it's just too useful for things beside web browsing.
I certainly don't understand folks getting lots of crashes.
I don't think refreshes have stopped but I don't open lots of tabs myself so I should be OK with that since I was before 7.1 anyway.
Here's hoping 7.1 fixes crashes for people or at least minimizes what they previously encountered. I see no reason why if anyone is dissatisfied why they cannot bring it to Apple since 7.1 was released if the problems continue with crashing. Tab reloads may definitely be an entirely different story but I'm not going to be looking for trouble any longer with that either.
Nin.com? What's that?
Nin.com was one of the trouble sites that everyone referred people too if they wanted to see their Air crash.
I agree with you, hopefully this does smooth things out on safari so more people are happy.
Nin.com was one of the trouble sites that everyone referred people too if they wanted to see their Air crash.
I agree with you, hopefully this does smooth things out on safari so more people are happy.
and still is...
nin.com crashes my iPad Air every time.
Yes sir. I've had pretty good luck with my Air and safari but this site did send me back to the home screen fairly quickly. That's pretty much the only one that has thus far. Apple.com, social living, etc, etc are all fine no matter what pinching or zooming or scrolling I did. Nin.com barfed almost immediately.
Good thing I have zero reason to go there ever.
7.1 on my air, after about 3 hrs usage, refresh problem still exist. not 1 crash so far so i guess they fixed sth, but the refresh problem gets annoying after a long use
Yes, according to my own tests, Safari still unloads pages just to avoid crashes during loading of new pages.
Nevertheless, it's still far superior to the 7.0.x implementation - it only crashes far later.
----------
It shouldn't crash it after a full reboot, which results in, according to my own memory tests done under b5 on the also-64bit rMini, 500+ Mbytes of free RAM.
(The 500Mbyte is the lower limit I've measured. After some memory crashes, during which iOS significantly increases the free RAM, the free RAM may become even as large as 710Mbytes. Nevertheless, this never happens after a fresh reboot - mass-scale allocations and even crashes are explicitly needed to free up as much RAM as possible. Just like under all previous iOS versions, for that matter - iOS has always behaved this way, and 7.1 didn't change this behaviour.)
----------
It all depends on what runs in the background. If you manually kill all previous tasks (or, even better, reboot the entire thing), you can minimize the chance of subsequent crashes. Until you load too many pages and/or start executing other apps, that is.
The only way for the tab reloading issue to get solved is if Apple:
In the meantime people can discuss about how much better this problem has become or not. The fact is that nothing has really changed.
Accept it and use your iPad accordingly, or don't and find a different way to browse the Internet.
I have chosen the latter and use OS X devices instead. I only rarely try to use my iPad for Internet surfing..
- Starts using more RAM on its devices
- Optimize Safari in a way that unloading pages from memory isn't needed
In the meantime people can discuss about how much better this problem has become or not. The fact is that nothing has really changed.
Accept it and use your iPad accordingly, or don't and find a different way to browse the Internet.
I have chosen the latter and use OS X devices instead. I only rarely try to use my iPad for Internet surfing..
....or they implement Safari the way they used to in iOS6! I never experienced crashing back then!
They have just coded a bloated and RAM-hungry new o/s. Then left us to it.
In iOS 6 we had almost no crashing, but tab reloading has been with us since the beginning of Mobile Safari. It is unfortunately nothing new.
I never used to experience tab reloading. Only since iOS7. I'm not disputing that others did but I myself did not.
Sorry, but you're wrong. I've done tons of benchmarks and found out that
- Safari in iOS6 is as prone to crashing as in iOS7.0.x
- iOS7.0.x, contrary to the popular belief, does not consume (significantly) more RAM than iOS6.
----------
It was as big an issue as in 7.x in all previous iOS versions.
Not referring to you, but I suspect lots of people don't even understand what "tab reloading" means. Or perhaps they never use more than one tab when using Safari. To me, "Open in *background* tab" is essential functionality.
The SW and HW are identical in all iPad Airs, so if it happens for some people, if happens for all, when the usage pattern is the same.
If you have a really fast connection and the pages you have open are not "heavy", you don't necessarily notice much of a delay when switching between them, if a reload occurs. But it's a reload nonetheless, resetting everything you were doing in that tab which is really annoying.
The least Safari could do is to remember the location, so there would be no need to scroll back...
They will. They just prefer planned obsolescence; hence the lack of RAM even in their latest-gen 64-bit devices. Which is a real PITA as Safari (and UIWebView) tended to allocate 20-30% more RAM under 7.0.x upon loading the same page on a 64-bit device than on a 32-bit one, assuming otherwise the same circumstances (iOS version etc.).
That is, Apple did know beforehand the new iPads 64-bit will behave significantly worse than old 32-bit ones under 7.0.x because of the RAM memory usage increase. Still, they refused to add additional RAM. After all, they need to sell this year's forthcoming models, which are sure to have 2+GB of RAM.
Last edited:
I always have the maximum number of tabs open and honestly never used to have page reloads. Perhaps if I limit the number of tabs open in iOS6 to six, it will perform like it did in iOS6?
Again: you've done something wrong. In no way did Safari under iOS6 behave significantly better than under iOS7.