Firefox performance sucks!
rodd at clarkson.id.au
Wed Aug 29 00:33:22 UTC 2007
On Wed, 2007-08-29 at 08:23 +1000, Rodd Clarkson wrote:
> On Mon, 2007-08-27 at 09:57 +0530, Rahul Sundaram wrote:
> > Rodd Clarkson wrote:
> > > I'm not sure what to look for in the prefs.js file, but if someone else
> > > is intersted in grabbing my original (broken?) prefs.js file and trying
> > > it on their install (to see if it causes the same grief) then that might
> > > be interesting to do.
> > >
> > > Should I file a bug against this?
> > Maybe in Mozilla Bugzilla but I foobar'ed my configuration and I have no
> > idea what's wrong with it doesn't really make up for a good bug report.
> > If it wasn't custom configurations then it might make sense to do that.
> That's the thing. I didn't Foobar my prefs.js file. In fact, I've only
> ever changed a few things in it and they didn't affect performance at
> the time.
> Something has changed in firefox/seamonkey that now doesn't like
> something in my prefs.js file and which is affecting performance.
> In fact, it appears my wife is having the same issues too, and she's
> never touched her prefs.js file (she wouldn't know what it was or where
> to find it).
> In short: this isn't something I've done.
> I'm going to find out if my wife's prefs.js file in bunk and then file
> upstream at firefox.
Sorry if I sound like I'm mumbling, I've got a mouthful of humble pie.
A big thanks for David Timms for trying out my prefs.js file and showing
me the error of my ways.
Turns out, I had a proxy set up and this was causing the problem. I
reverted back to my original prefs.js file and turned of proxying (which
I don't need and wasn't using since there was no way the proxy it was
set up for would be visible from my home) and all it good now.
What is strange is that this problem only manifested in the past few
months. The url I had in my proxy settings was for a business I worked
for some 18 months ago and at the time I set it up it caused me no
problems when I was using the Internet at home and at other places. The
url was only visible internally. Something in firefox/seamonkey has
changed recently that has made this more of an issue, but it didn't need
to be set up anyway so I've turned it off.
Is it worth looking into whether firefox should cope better if you set
up an proxy with a 'bad' url in it?
"It's a fine line between denial and faith.
It's much better on my side"
More information about the test