Macworld Forums

Macworld Forums: Webpages Not Responding - Macworld Forums

Jump to content

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Webpages Not Responding Persistent bug in Safari 5.1.x and 6.0.x

#1 User is offline   mklprc 

  • Newbie
  • Pip
  • Group: Members
  • Posts: 4
  • Joined: 17-February 08

Posted 07 January 2013 - 03:16 PM

What is going on with the Safari team? Starting with 5.1.0 a new bug was introduced which included this dialog box:

Posted Image

It has not been fixed in any version since. It stayed in when upgraded to 6.0 and is still there in 6.0.2. Almost all other Safari users I have talked with have experienced it.

It usually appears when I have 3 or 4 windows open at once and then try navigating between links (or back to a previous page). I can Cancel to avoid the Force Reload, but unless I close ALL windows it will eventually make me reload. Since I have several tab groupings of my favorite web-comic sites, and news sites, this bites me every day.

As a result I warn all my clients to stop with version 5.0.5 or so, but this doesn't help Lion/ML victims, who can't downgrade.
0

#2 User is offline   bastion 

  • Power User
  • PipPipPipPip
  • Group: Members
  • Posts: 9,094
  • Joined: 14-October 04

Posted 08 January 2013 - 03:13 AM

View Postmklprc, on 07 January 2013 - 03:16 PM, said:

What is going on with the Safari team? Starting with 5.1.0 a new bug was introduced which included this dialog box:

...

It has not been fixed in any version since. It stayed in when upgraded to 6.0 and is still there in 6.0.2. Almost all other Safari users I have talked with have experienced it.

It usually appears when I have 3 or 4 windows open at once and then try navigating between links (or back to a previous page). I can Cancel to avoid the Force Reload, but unless I close ALL windows it will eventually make me reload. Since I have several tab groupings of my favorite web-comic sites, and news sites, this bites me every day.

As a result I warn all my clients to stop with version 5.0.5 or so, but this doesn't help Lion/ML victims, who can't downgrade.


You're doing your clients a disservice.

First: Understand that this "bug" exists in 5.0.x as well; it just doesn't give the user the option of not reloading. The dialog was added in response to user complaints about that.
Second: Also understand that generally when you see this message what it means is that a 3rd-party plugin has hung or died while rendering part of the page content for which it's responsible. You may recall a few years ago Apple noting that a single Safari plugin was the source of most of the support calls they were getting.

You'd be helping your clients more if you advised them to use ClickToFlash.
0

#3 User is offline   icerabbit 

  • Veteran
  • PipPipPip
  • Group: Members
  • Posts: 2,111
  • Joined: 28-March 02

Posted 09 January 2013 - 05:24 AM

Bastion is right, that it probably has to do with Flash or some other site's fancy scripting.

I've been seeing plenty of page loading issues with browsers as well. Oddly enough I have not seen that exact error.

What it indicates to me, when it says that it will need to reload all pages, is that Safari's sibling process called "web process" is timing out. It used to be Safari itself would fall to its knees on older systems when Safari used 1GB of RAM. Then they split it up into Safari & Web Process. Safari remains manageable but Web Process mushrooms. On newer systems the margin is higher, but on my Core i7 it will approach 2GB before I can't tolerate it any more. Maybe if I was more patient and carried on, that error would actually appear on screen.

Loading a dozen mainstream sites across some tabs, plus a couple other windows with searches and tabbed results; could do you in within an hour. And which mainstream site doesn't use flash for ads, video, etc? This would go hand in hand with lots of page out activity to the hard drive. I then go to Activity monitor. Force-quit Web Process. Windows & pages reload. All is well again for another few hours of intense browsing.

Since I don't use plug-ins or extensions in Safari - other than having flash installed on the computer for all browsers- and Firefox hasn't exhibited this behavior for me - it surely has to do with Safari not handling things so well and not cleaning up after itself. If for the sake of simplicity every fancy web bloated page were 1 MB each, then there's no reason web process should go above a few hundred MB.
0

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

2 User(s) are reading this topic
0 members, 2 guests, 0 anonymous users