I get what he was saying, will people still complain now that we got 2GB RAM and when it purges Safari tabs with more apps opened. It's about meeting expectation within reasonable limits; that expectation has been met with the Air 2.
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.
iPad So does the 2GB of RAM fix Safari refresh?
- Thread starter nikhsub1
- Start date
- Sort by reaction score
I get what he was saying, will people still complain now that we got 2GB RAM and when it purges Safari tabs with more apps opened. It's about meeting expectation within reasonable limits; that expectation has been met with the Air 2.
And until the Air 2, that was our only choice. Although some of us had more than "some" tab reloading.
100% agree. If Safari is more usable, without having to worry about constant reloads by adding 2GB Ram....great!
Apple doesn't need apologists. They are doing just fine despite the fringe whining. Nice try though.
It's great that another GB of RAM helps Safari's reloading issues.
Unfortunately, this solution only helps people who buy a new iPad. Throwing hardware at a software problem can work to a limited degree, but isn't the right solution.
Of course the RAM limits how much can be loaded into memory at once. But the idea that 1 GB isn't enough for two average websites is ridiculous. Somehow Chrome, another webkit-based browser, can handle a lot more.
Anyway, a moot issue now. I have zero hope Apple will fix Safari now. I'll just have to get used to using a different browser.
So why is it okay or even excusable for Apple to release hardware with insufficient RAM to run their own native browser? It would have only cost a few dollars per device to add 1G RAM to original iPad Air and iPhone 6/6 Plus and would have provided a much better Safari experience. I would have gladly paid the difference. As things stand, my top-of-the line LTE iPad Air has irritated me to no end for an entire year with the constant reloads and app crashes. I would have returned the danged thing last fall if I hadn't already gifted my iPad 3 to a family member. They've pulled the same crap with this year's 6 Plus.
Doesn't it make you want to trade in your 6 plus next year when the 6s plus has 2GB of RAM? If so, then Apple's strategy worked. If they had put it 2GB in the plus, you would probably skip the 6s.
Because it's sufficient. The browser works. They've decided to implement an aggressive tab purge design. You should be used to this by now. Apple decides what's good for you. If you want something different, you need to explore other non-Apple options.
So does the 2GB of RAM fix Safari refresh?
Yes but I am getting more than tired of this approach. One of these days Google/Android may get my business. I guess that's a big maybe - I've threatened the past few years but never make the jump. I would have definitely considered the Note 4 this year if they had offered a pure Google version but I can't abide TouchwhiZ or the carrier bloatware. I do have quite a few friends/family members who are not compelled (serial) upgraders whom I advised last year to hold off on iPad Air and this year to wait until next year for a new phone. I guess it works for Apple's bottom line but they alienate long-term users.
----------
Being used to it doesn't make it a good experience. I've switched to Chrome and it's better with the reloads but like others I prefer integrated browsing among all my devices via iCloud.
But hey, I plan to offload original Air on unsuspecting family member and buy Air 2 if Black Friday deals are good
. Hopefully it will have long shelf-life like iPad 2. I bought those for my parents and in-laws years ago and they are still going strong.
Yes but I am getting more than tired of this approach. One of these days Google/Android may get my business. I guess that's a big maybe - I've threatened the past few years but never make the jump. I would have definitely considered the Note 4 this year if they had offered a pure Google version but I can't abide TouchwhiZ or the carrier bloatware. I do have quite a few friends/family members who are not compelled (serial) upgraders whom I advised last year to hold off on iPad Air and this year to wait until next year for a new phone. I guess it works for Apple's bottom line but they alienate long-term users.
----------
Being used to it doesn't make it a good experience. I've switched to Chrome and it's better with the reloads but like others I prefer integrated browsing among all my devices via iCloud.
But hey, I plan to offload original Air on unsuspecting family member and buy Air 2 if Black Friday deals are good
. Hopefully it will have long shelf-life like iPad 2. I bought those for my parents and in-laws years ago and they are still going strong.
Not being a good experience is NOT the same as not working. That's what some people can't grasp around here.
Apple makes design decisions. You either live with them or you jailbreak or go Android. It's as simple as that.
I remember when the iPhone was released. It had no copy and paste. NO COPY and PASTE!!! For crying out loud. So there. Take it or leave it. I took it. The phone still worked. It was not a good experience.
So complaining about the lack of RAM is futile. The iPad works. Safari reloads. Chrome reloads less. iCab even less. It's the nature of iOS. An extra GB of RAM may make it reload less, but obviously Safari was programmed (or is buggy) to aggressively purge tabs from memory. So now we have 2GB of RAM. And now it reloads less, but still reloads. Why? Because it has to. RAM is not unlimited, even in systems with 16GB of RAM. And this is just a TABLET. Not a PC.
So the incessant complaining and blaming hardware for a software issue and possibly even a design decision by Apple is grating. Hopefully we can now leave this non-issue behind and focus on more important things. Like the gamut. Or book spines. Or yellow tint. Or vibrations. Or bending. Or dropped WiFi. Or....
Yep. I've argued so much with people on this forum who think software can magically solve a hard limitation due to paltry ram that I've grown so tired of it, now we all know who's right.
No I'm not, the only way you are going to have tabs not reload when you have that pathetic amount of ram is flashing them to flash storage which apple has never done and as far as anyone knows has absolutely no plans to do. So no I'm not wrong, and in fact you all like zboater and surf monkey who keep spewing this same **** constantly when you have been proven wrong by this device with 2gb of ram is laughably stupid.
Wow, aggressive.... Chill out.
The additional RAM does help. But the problem Is a combo of low RAM AND software. Now the RAM part has been addressed it's going to perform better. Now it's up to Apple to fix safari.
Those who don't know history are doomed to repeat it.
Back in the 80's and 90's memory compression software existed since DRAM cost was through the roof but it had drawbacks such as higher CPU overhead and latency and would've had an impact on battery life. Forward to today it probably costs a few bucks at most for 2GB DRAM versus hiring a team of developers and the lesser experience with a software work-around.
Don't know why people are still apologizing when even Apple stopped with the iPad Air 2.
Back in the 80's and 90's memory compression software existed since DRAM cost was through the roof but it had drawbacks such as higher CPU overhead and latency and would've had an impact on battery life. Forward to today it probably costs a few bucks at most for 2GB DRAM versus hiring a team of developers and the lesser experience with a software work-around.
Don't know why people are still apologizing when even Apple stopped with the iPad Air 2.
It's nothing to do with software! It's intentional that it reloads when you run out of ram and any device will eventually run out of ram if it doesn't cache to storage! That's how it is! You can't magically store tabs in the air. It's a question of when you reach that point and if it's acceptable! And with one gigabyte it's not.
Welp, I'm on my iPad Air 2, and I had two tabs open: this forum, and this web page. Two things happened:
1. The tabs reload when I switched between the two pages.
2. The first time I tried to reply to this thread, Safari froze when I tried to add the link above, wouldn't respond to anything. I had to force quit safari, respring, and then I was able to post to this thread the way I wanted.
Ironically, I don't ever remember having that bad of a problem on my Air, which my significant other now uses. And it didn't have a problem with reloading these two tabs.
I still think there's a bug in Safari. Having 2GB is a bandaid that gets around the poor memory management, in SOME cases, FOR NOW. But it's not the real fix.
1. The tabs reload when I switched between the two pages.
2. The first time I tried to reply to this thread, Safari froze when I tried to add the link above, wouldn't respond to anything. I had to force quit safari, respring, and then I was able to post to this thread the way I wanted.
Ironically, I don't ever remember having that bad of a problem on my Air, which my significant other now uses. And it didn't have a problem with reloading these two tabs.
I still think there's a bug in Safari. Having 2GB is a bandaid that gets around the poor memory management, in SOME cases, FOR NOW. But it's not the real fix.
It's should be Safari bug because I'm using Nexus 5 which has 2GB of RAM and it doesn't reload tabs in my browser.
Ok. So you are saying you HAVE tried other browsers and STILL have the same issue?
You probably have other apps opened which would make it worse. From a scientific approach with having only Safari opened 2GB DRAM does make a huge difference.
That is because it is impossible to not be if you don't cache to storage my god that's not a bandaid it's called that's the way it works unless you fundamentally change the ******* WebKit. Most browsers (I can't think of any mobile one) don't cache to storage.
It's not a bandaid it's like that due to speed I imagine and the amount of memory you have to use with safari on a device with 1 gb of ram is pathetic.
Wait, wasn't more RAM supposed to fix THAT problem, too? That's what people were were saying in the iPad Air days. COnstantly having to quit apps because there supposedly isn't enough RAM.
So now 2GB isn't enough? How much is then? 4GB? 8? 16?
But from an empirical approach, that's not the true solution. More RAM accomodates bloat for a bit longer. The real solution is better memory management... in software.
Exactly. Safari performance was acceptable back on the iPad 4 with iOS 6. Then came the iPad Air with its fancy pants 64bit processor and OS with a bigger memory foot print, 1GB was no longer acceptable. On the iPad Air on iOS 7, there was nonstop low memory errors in the diagnostic logs. Then came iOS 8 those low memory errors were replaced with endless "stacks + backboard", which I'm guessing is Apple's sneaky way of hiding low memory errors.
On the Air 2, there is not a single one of those stacks + backboard error. In fact the diagnostic log is empty save for 3 "jetsamevent".
Right now I have this open as I'm replying, your t mobile page, the verge, Best Buy, and Engadget opened. I just flipped to each tab, in the middle of typing this, flipped back here to continue typing, and I didn't have to re type the whole thing.