[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: firefox is regularly dying



On Sat, 18 Apr 2009, Greg wrote:

> On 18/04/2009 6:55 PM, Robert P. J. Day wrote:
> > On Sat, 18 Apr 2009, Martin Sourada wrote:
> >
> >
> > > >  On Sat, 2009-04-11 at 05:19 -0400, Robert P. J. Day wrote:
> > >
> > > > >  >  as of earlier this morning, firefox has simply aborted when i try
> > > > >  >  to do nothing more than follow a perfectly decent link.  it's
> > > > >  >  happened three times in the last 20 minutes.  is anyone else
> > > > >  >  seeing firefox just going away for no reason?
> > > > >  >
> > > > >  >  $ rpm -q firefox
> > > > >  >  firefox-3.1-0.11.beta3.fc11.x86_64
> > > > >  >  $
> > > >
> > > >  Looks like there is xulrunner at fault... Epiphany is regularly
> > > >  dying for me as well (though at first glance I do not see to
> > > >  experience it as often as you do). This is for the first time
> > > >  WebKitGTK is stabler than gecko for me... Actually the webkitgtk
> > > >  version in rawhide is rock stable... I suggest you try it out,
> > > >  midori is pretty interesting web-browser.
> > > >
> > > >  $ rpm -q xulrunner
> > > >  xulrunner-1.9.1-0.11.beta3.fc11.i586
> > >
> >    i have effectively given up on firefox.  it used to be annoyingly
> > slow, but annoyingly has lately turned into agonizingly, where FF
> > regularly sucks up 100% of the CPU according to "top" (admittedly on a
> > core 2 duo system).
> >
> >    in fact, at the moment, firefox is listed as using just over 118%
> > of the CPU, whereas seamonkey is sitting down around 0.3%.  i used to
> > really like firefox.  how did it turn into such an unmitigated
> > disaster?

> what Extensions/Themes are you using in Firefox? cause i dont see
> that

  this is firefox-3.1-0.11.beta3.fc11.x86_64, running pretty much out
of the box on a fresh install of f11 beta x86_64, with the 64-bit
adobe flash player installed in /usr/lib/mozilla/plugins and that's
all.

  i just started FF and am not doing *anything* with it -- it's just
sitting there, and top reports that that single invocation of FF is
using 103.3% CPU, while multiple invocations of seamonkey are taking
up a total of 3.3%.

  i'm not the only person who's reported on this -- firefox is just
horribly, horribly slow.  i just switched virtual desktops to check on
that one FF window, and what i get is a FF-sized window that still
contains the content from the previous virtual desktop -- my system
isn't even capable of refreshing the FF window, while seamonkey just
zips right along.

  others might not be seeing this, but at the moment, FF is unusable
for me.

rday
--

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

        Linux Consulting, Training and Annoying Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Linked In:                             http://www.linkedin.com/in/rpjday
Twitter:                                       http://twitter.com/rpjday
========================================================================


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]