I can't even visit Macrumors on my phone without seeing this error every single thread multiple times. I am getting very frustrated with the error happening so frequently on so many sites. Yesterday I erased my phone and started fresh to see if it helped, but it didn't. Still happening way too frequently. I have an iPhone 6+ 64g running 8.4, it's been happening for weeks now. Trying to figure out if it's the phone or iOS.
Got a tip for us?
Let us know
A problem has occurred with this webpage so it was reloaded. Way too often, especially on this site.
- Thread starter Brocksley
- Start date
- Sort (Likes)
It all depends how long you browse for and which sites you visit. I experience it two or three times per day but one thing's for sure, my old iPhone 5 didn't do it on the same sites. It must be an iOS8 issue.
For me, this problem happens on sites that are heavy Javascript sites. I don't know if the Forums use Javascript, but I can't recall having this issue here.
I'm on 8.4 on an iPad3. I have Frisbeed my iPad more than once because of this problem ever since IOS8 came out. I wonder if my iPad3 is just too underpowered to handle the rendering requirements of Javascript, which seem to have increased a lot in this release.
I'm on 8.4 on an iPad3. I have Frisbeed my iPad more than once because of this problem ever since IOS8 came out. I wonder if my iPad3 is just too underpowered to handle the rendering requirements of Javascript, which seem to have increased a lot in this release.
No clue. I've never seen this problem with my 6+ on any site. Only with my iPad3. I have to say, my 6+ is really an incredible device. I honestly can't remember having any problems with it at all, which I know is different from a number of posters here. I can easily believe that IOS8 was designed for the 6 and 6+, and Apple didn't give two hoots about older hardware like my iPad3. In fact, I could be convinced that Apple had some intent to make IOS8 run like poo on older devices as an inducement to upgrade. This issue from the OP is the result of that.
Do you browse heavily and for extended periods on your 6+, or do you save that kind of session for your iPad? I use the heck out of my 6+ and encounter loads of problems; mainly app/browser reloading and webpage crashing with the occasional daily springboard crash.
Generally, my iPad is my primary browsing device. I can't stand the mobil site formats you get by default on the 6+. And the phone screen is too small to use full site formats, at lease IMO. But I will browse on my phone because that's the device I carry around with me. So, I guess I don't use my phone to the same degree you do. I tend to use it primarily as, you know... a phone.
I don't know how often this issue happens on newer iPads. I suspect it does, but I'd think that the newer processors and increased RAM might minimize this issue.
The 6+ is a 'phablet' though and is supposed to be much more of a useful browsing tool.
Other than the nice large screen, I find the cogs and wheels inside the device to be much worse for browsing than my old i5.
I appreciate your beef with mobile sites. On the worst offenders I switch to the full website and personally have no problem with screen real estate. I'm used to scrolling and pinch/zooming.
The whole phablet thing was one reason I got the 6+. I had a 5 and it worked very well, but I'm a gear head at heart and had to have the latest and greatest. The other reason I got it was the camera, and I use that a lot. Very nice. But the 6+ doesn't replace the iPad for me. I view them as complimentary devices. I'm interested in the iPad Air 3 coming out this fall, though. I never thought I'd consider upgrading my iPad given the scurrilous path to obsolecence Apple puts older devices on, but I played around with an Air 2 recently, and was really impressed. The Air 3 will be just that much better.
I'm experiencing the reloads as well. That's probably Apple Music, or the Music App. Try to force quit the Music app while you're in Safari.
We'll have to wait for Apple to fix this mess.
Even if you're not running it at the moment, you should run it and then force quit. It worked for me.
I see this happen more on these forums than any other website. I think especially in posts with images. Since the forum update, people can post massive images, which I think might be one of the culprits.
