headers
Dr. Andrew J. Malton | 18 Apr 2007 17:40
Picon
Picon
Favicon

(no subject)

Lately I've been experiencing a lot more beach-ball time using OG  
5.5.3.  When pulling tabs off a page of links, each one (despite not  
actually being displayed) seems to occasions several (10, 15, 20)  
seconds of beach ball.  Which kinda defeats the purpose of firing off  
a collection of interesting tabs and looking at them in the order  
they arrive.  Or a new page will hang for a few seconds.

The simplest consistent explanation is that certain kinds of resource  
on some pages cause OG to hang while they are being downloaded.  But  
I can't imagine why that would be true.

This is a not a bleeding edge machine, but 733Mhz / 1Mb surely ought  
still to be enough.

Anyone else getting this behaviour?  Is it caused by something I can  
fix, like caches or disk disorganization?  I have no unusual extensions.

Help appreciated.
Permalink | Reply | 2 comments |
headers
Derek Currie | 18 Apr 2007 22:25
Picon

Re: Beach Ball Time


On Apr 18, 2007, at 04/18, 3:00 PM, "Dr. Andrew J. Malton"  
<ajmalton <at> uwaterloo.ca> wrote:

> Lately I've been experiencing a lot more beach-ball time using OG  
> 5.5.3.  When pulling tabs off a page of links, each one (despite  
> not actually being displayed) seems to occasions several (10, 15,  
> 20) seconds of beach ball.  Which kinda defeats the purpose of  
> firing off a collection of interesting tabs and looking at them in  
> the order they arrive.  Or a new page will hang for a few seconds. . .

My experience is that the more stuff you have OmniWeb hanging onto as  
resources the more likely this is to happen. When I install OW  
totally clean on a machine, with of course my massive bookmark  
collection, the thing runs just fine. But with time it gets more and  
more likely to go into 'beach ball' or what I call 'sit and spin'  
mode. I suspect OW is getting bogged down with too many things to  
keep track of. There are articles about how Safari gets bogged down  
with resources, one of which is from last week on MacFixIt. I bet the  
same thing is happening to OW.

The first thing I do is hit 'Flush Cache'. This can in and of itself  
lead to a considerable sit and spin session, but it helps a lot. It  
is incredible the amount of cache crap web browsers collect.

The second thing I do is shut down tabs and windows, simplifying what  
OW has to handle as much as possible.

The third thing I do is to get off whatever websites I am currently  
on in case they are CPU or thread hogs. It amazes me that in this day
(Continue reading)

Permalink | Reply | 0 comments |

Gmane