[Karl Buckland]

I've been reading that some people are having problems with Firefox 2. Common problems seem to be random freezing, bugs with the history bar/panel and that the RSS feed handling has taken a step backwards. Someone has even gone as far as to list 9 reasons not to use Firefox 2, at least until some of the problems are fixed.

As I've previously mentioned, I'm a little underwhelmed by the release, as I simply don't think that the changes made justify a new version number. There are still fairly big memory leak issues and many people have reported that many/all of their extensions no longer work. With the reputation that Firefox has built up for being an extensible browser, this is obviously a problem.

I don't use Firefox as my main browser, so I haven't come across these problems myself. It seems faster to launch than the previous version, which is obviously a good thing, but I can't tell much more than that without using it more. So, how is everyone else finding it?

[marcamos]

Yeah, I have only experienced one problem with the new Firefox; it was earlier today on my fiance's dad's Dell (XP Home). We had just installed FF 2.0 and he then went to his home page, which is the Google Personalized home page. 3 times in a row, a visit to that page made FF crash, and 3 times in a row I felt like a fool for recommending that he install "the new FF 2.0".

On the flip-side, I have had no problems with FF 2 on my system... so hmmm. I do agree though, now more than before, this release didn't deserve the 'version 2' name.

[moojoo]

May be windows more so than FF. I use it on XP Pro at Work and Tiger on my laptop and have not had any issues on either. I wouldn't be suprised if a lot of the "problems" are related to some misc windows software or windows components.

[Karl Buckland]

Well, to be fair, quite a few of the problems such as the History bugs and RSS feed handling are obvious Firefox issues and cannot be blamed on the OS. Also, again, to be fair, if Firefox 1.5 works on a particular setup, why shouldn't Firefox 2?

[moojoo]

Are they happening in all FF 2.0 releases or just on Windows? I haven't experienced any of them on mac or windows though..

This post has been edited by moojoo: 30 October 2006 - 03:28 PM

[marcamos]

My FF for Mac has been error free, and the winders version only had that one quirk I mentioned above on google.com/ig/

[moojoo]

Well to clarify my earlier post, I am just curious to know if people having specific problems have the same kind of setup and/or certain software packages that may be conflicting. of course it just could be an oops in the ff source as well. But since it only happens to certain people I am just interested heh. Like does it only happen when IE 7 is installed or does it happen with IE 6 installed? Stuff like that.

This post has been edited by moojoo: 31 October 2006 - 08:51 AM

[marcamos]

Good call; to explain in a little more detail the situation the computer was in when I experienced my google.com/ig/ issue:

A fresh install of FF 2 over FF 1.5, literally only minutes before. The old FF 1.5 had *no* plugins; it also was a default install.

IE6 was also on the system, but no IE7.

A mostly default install of XP Home was on the computer, and it's owned by an older person (my fiance's dad), and while he is proficient, he doesn't modify much, or know of uber-l33t software that could cause headaches.

I'm just guessing it was a little bug that either Google will fix (assuming it happens to all FF 2 users), or something that FF will hear about and fix in an update.

[moojoo]

Brings up another point.

XP Home, XP Pro etc etc.. Does it happen more on one than the other? And granted the OS X version seems to be bug free at least in this scenario.. But since FF is not a Cocoa app, I don't see the code base being that different between the OS X and Windows versions. Maybe I am wrong? Just would be interesting to do our own little study/comparison see if we can't perhaps find a root to the cause if not a solution.

In my case I just installed 2.0 over 1.5 on XP Pro at Work and XP Pro on my Mac and under OS X and have none of the bugs reported. So that is two completely different hardware sets running windows. Only similarity is the OS.

This post has been edited by moojoo: 31 October 2006 - 09:12 AM

[ShakingSpirit]

A guy whose blog I read (http://www.jonwatson.ca/node/1101) also has the random freezing issue on a Linux box. Doesn't seem to be a Windows-only problem

This post has been edited by ShakingSpirit: 31 October 2006 - 03:08 PM

[william]

No probs here on a standard Windows XP Pro - in fact I was getting the odd browser crash and slow down with 1.5 but that seems to have vanished with 2.0.

This post has been edited by wgardner: 31 October 2006 - 06:49 PM

[MegaManX]

using xp pro
have installed about 15 extensions
a 3 year old computer
15 or so tabs and 130mb of memory
I don't think that's too bad
no problems here

[marcamos]

MegaManX, on Nov 12 2006, 10:53 PM, said:

using xp pro
have installed about 15 extensions
a 3 year old computer
15 or so tabs and 130mb of memory
I don't think that's too bad
no problems here

Wow, with all those extensions and tabs, I'd say you're using it to it's fullest potential!

[moojoo]

Wonder if its hardware related. A long shot sure but if it happens on a Linux as well I wonder if they are running similar hardware.

[TJSingleton]

It seemed to crash/hang a bit after first install, but not lately -- maybe it was a problem with extensions?

This post has been edited by TJSingleton: 22 November 2006 - 10:41 PM

[howtodress123]

I have only experienced one problem with the new Firefox; it was earlier today on my fiance's dad's Dell (XP Home). We had just installed FF 2.0 and he then went to his home page, which is the Google Personalized home page. 3 times in a row, a visit to that page made FF crash, and 3 times in a row I felt like a fool for recommending that he install "the new FF 2.0".

How To Dress For Your Body Shape

This post has been edited by howtodress123: 22 August 2011 - 09:34 AM