Just out of curiosity, has anyone noticed a problem that has developed with firefox? This started on both of my machines after the newest updates. I'll be at a website, even the mozilla website, and when I click on a link to go to another part of the site or to download a file, Firefox will just simply close. It's random for the most part, but it happened quite often at the sourceforge.net website too. I'm not having this problem with Seamonkey.
Jim
Jimmy Bradley a écrit :
Just out of curiosity, has anyone noticed a problem that hasdeveloped with firefox? This started on both of my machines after the newest updates. I'll be at a website, even the mozilla website, and when I click on a link to go to another part of the site or to download a file, Firefox will just simply close. It's random for the most part, but it happened quite often at the sourceforge.net website too. I'm not having this problem with Seamonkey.
I'll second this. Firefox seems to crash all the time now. I'll try to perform a harmless action like log in to my webmail or post a message in a forum, and woosh, it's gone. This is beginning to be a bit unnerving.
One question, by the way: how did you install Seamonkey? Did you install the tarball from mozilla.org?
Niki
On Fri, 18 Jan 2008, Niki Kovacs wrote:
Jimmy Bradley a écrit :
Just out of curiosity, has anyone noticed a problem that hasdeveloped with firefox? This started on both of my machines after the newest updates. I'll be at a website, even the mozilla website, and when I click on a link to go to another part of the site or to download a file, Firefox will just simply close. It's random for the most part, but it happened quite often at the sourceforge.net website too. I'm not having this problem with Seamonkey.
I'll second this. Firefox seems to crash all the time now. I'll try to perform a harmless action like log in to my webmail or post a message in a forum, and woosh, it's gone. This is beginning to be a bit unnerving.
One question, by the way: how did you install Seamonkey? Did you install the tarball from mozilla.org?
Firefox is a very popular cross-platform browser.
What are people's thoughts of Opera, which is in the same category?
Scott
Niki _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
I installed Firefox 2.0.0.x in an effort to stop this problem, but it still happens just not as frequently. I have heard it doesn't happen in Firefox 3, along with a few other annoying traits that have developed in the Firefox line. I have tried Opera on the machine that Firefox was crashing on and it seemed to help at first but then it got progressively slower to the point of being unusable. There is a discussion in this list recently of the same type issues with Seamonkey.
On Jan 18, 2008 6:41 AM, Scott Ehrlich scott@mit.edu wrote:
On Fri, 18 Jan 2008, Niki Kovacs wrote:
Jimmy Bradley a écrit :
Just out of curiosity, has anyone noticed a problem that hasdeveloped with firefox? This started on both of my machines after the newest updates. I'll be at a website, even the mozilla website, and when I click on a link to go to another part of the site or to download a file, Firefox will just simply close. It's random for the most part, but it happened quite often at the sourceforge.net website too. I'm not having this problem with Seamonkey.
I'll second this. Firefox seems to crash all the time now. I'll try to perform a harmless action like log in to my webmail or post a message in a forum, and woosh, it's gone. This is beginning to be a bit unnerving.
One question, by the way: how did you install Seamonkey? Did you install the tarball from mozilla.org?
Firefox is a very popular cross-platform browser.
What are people's thoughts of Opera, which is in the same category?
Scott
Niki _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Dan wrote:
I installed Firefox 2.0.0.x in an effort to stop this problem, but it still happens just not as frequently. I have heard it doesn't happen in Firefox 3, along with a few other annoying traits that have developed in the Firefox line. I have tried Opera on the machine that Firefox was crashing on and it seemed to help at first but then it got progressively slower to the point of being unusable. There is a discussion in this list recently of the same type issues with Seamonkey.
I was having this problem, which was brought up in this thread here:
I, same as you, tried to use 2.0.0.x and was having the same things happen, even after cleaning my profile and creating a new one.
I loaded Firefox 3 beta 2 and it hasn't crashed once on me. Perhaps try that one until someone can get to the bug.
Regards, Max
On Jan 18, 2008 6:26 AM, Max Hetrick maxhetrick@verizon.net wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Dan wrote:
I installed Firefox 2.0.0.x in an effort to stop this problem, but it still happens just not as frequently. I have heard it doesn't happen in Firefox 3, along with a few other annoying traits that have developed in the Firefox line. I have tried Opera on the machine that Firefox was crashing on and it seemed to help at first but then it got progressively slower to the point of being unusable. There is a discussion in this list recently of the same type issues with Seamonkey.
I was having this problem, which was brought up in this thread here:
<
http://grokbase.com/post/2008/01/08/centos-probably-ot-has-anyone-else-seen-...
I, same as you, tried to use 2.0.0.x and was having the same things happen, even after cleaning my profile and creating a new one.
I loaded Firefox 3 beta 2 and it hasn't crashed once on me. Perhaps try that one until someone can get to the bug.
Regards, Max
I had a similar problem in SeaMonkey a while back, reported it as a bug, got the nightly build of SeaMonkey from a week or so ago (I think I need a new one), and it performed just fine for a while. Now it has the same problem again, so don't be too quick to absolve Firefox - other users have noticed this, too.
I have sent in the crash dumps from this for analysis, so I suspect (hope?) that the mozilla gurus are on their way to a fix.
I'll post when this is resolved.
mhr
Dan wrote:
I installed Firefox 2.0.0.x in an effort to stop this problem, but it still happens just not as frequently. I have heard it doesn't happen in Firefox 3, along with a few other annoying traits that have developed in the Firefox line. I have tried Opera on the machine that Firefox was crashing on and it seemed to help at first but then it got progressively slower to the point of being unusable. There is a discussion in this list recently of the same type issues with Seamonkey.
I too noticed this problem. Went right to Firefox 3 and the problem miraculously disappeared.
Mark
I wondered why I wasn't having any problems, so I checked my version of Firefox and I'm still using 1.5. I'll upgrade to Firefox 3 and just jump over the Firefox 2.0.0 version.
Kind regards, Nancy
On Fri, 2008-01-18 at 13:30 -0500, Mark Weaver wrote:
Dan wrote:
I installed Firefox 2.0.0.x in an effort to stop this problem, but it still happens just not as frequently. I have heard it doesn't happen in Firefox 3, along with a few other annoying traits that have developed in the Firefox line. I have tried Opera on the machine that Firefox was crashing on and it seemed to help at first but then it got progressively slower to the point of being unusable. There is a discussion in this list recently of the same type issues with Seamonkey.
I too noticed this problem. Went right to Firefox 3 and the problem miraculously disappeared.
Mark _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Nancy Rudins wrote:
I wondered why I wasn't having any problems, so I checked my version of Firefox and I'm still using 1.5. I'll upgrade to Firefox 3 and just jump over the Firefox 2.0.0 version.
Kind regards, Nancy
On Fri, 2008-01-18 at 13:30 -0500, Mark Weaver wrote:
Dan wrote:
I installed Firefox 2.0.0.x in an effort to stop this problem, but it still happens just not as frequently. I have heard it doesn't happen in Firefox 3, along with a few other annoying traits that have developed in the Firefox line. I have tried Opera on the machine that Firefox was crashing on and it seemed to help at first but then it got progressively slower to the point of being unusable. There is a discussion in this list recently of the same type issues with Seamonkey.
I too noticed this problem. Went right to Firefox 3 and the problem miraculously disappeared.
Mark _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Stupid question... How does one upgrade to ff 3? Would that require installing via rpm off of ff's site?
J wrote:
Stupid question... How does one upgrade to ff 3? Would that require installing via rpm off of ff's site?
It's probably best to leave the RPM version alone. Just get the beta tarball from here:
http://www.mozilla.com/en-US/firefox/all-beta.html
Unpack it. Move .mozilla to .mozilla.orig (to preserve bookmarks and such in case something goes wrong. Add /home/<user>/firefox to the front end of the $PATH.
That's it.
Nancy Rudins wrote:
I too noticed this problem. Went right to Firefox 3 and the problem miraculously disappeared.
I'm running 2 and have experienced the problem, but I noticed that by installing the NoScript extension - it doesn't happen nearly as often.
My guess is the problem (or one of several) is JavaScript related. Last time it happened to me was on NewEgg - one of the sites where I allow script execution.
On Fri, 18 Jan 2008 21:22:52 -0600 Nancy Rudins nrudins@ncsa.uiuc.edu wrote:
I wondered why I wasn't having any problems, so I checked my version of Firefox and I'm still using 1.5. I'll upgrade to Firefox 3 and just jump over the Firefox 2.0.0 version.
Kind regards, Nancy
I'm really not sure what happened to FF 1.x & 2.x, but something got things all squirreled up.
Mark
Jimmy Bradley wrote:
Just out of curiosity, has anyone noticed a problem that hasdeveloped with firefox? This started on both of my machines after the newest updates. I'll be at a website, even the mozilla website, and when I click on a link to go to another part of the site or to download a file, Firefox will just simply close. It's random for the most part, but it happened quite often at the sourceforge.net website too. I'm not having this problem with Seamonkey.
I've heard a lot of complaints from Firefox/CentOS users. I never used CentOS as a desktop OS, so I can't confirm those issues from my own experience.
However, I use Fedora, Ubuntu and (very rarely) Windows XP as desktop OS, usually with the latest Firefox version and a set of plugins (Java, Flash, multimedia, Adobe) and extensions (SlimSearch [disclaimer: I'm the author], Forecastfox, Google Browser Sync, It's All Text, StumbleUpon, maybe others too) and the only issue I see is with 2.0.0.x slowly leaking memory. But there are no crashes.
It looks like the particular Firefox version distributed with CentOS / Red Hat has some serious issues.
My suggestion is to try a newer version. If you put it in /opt/firefox and add the bin/ subdirectory (or wherever the firefox binary is) to the front end of the $PATH variable, it will Simply Work with minimal changes. 2.0.0.x works fine for me on the abovementioned OS's. I've tried briefly 3.0beta on Ubuntu and Fedora and it seemed to work fine too, but I don't have much experience with it.
Bottom line: upgrade Firefox.
Maybe this should be put in the FAQ.
Florin Andrei wrote:
I've heard a lot of complaints from Firefox/CentOS users. I never used CentOS as a desktop OS, so I can't confirm those issues from my own experience.
I experienced a LOT of crashing with FireFox 2 in Fedora 8 but almost none using the tarball version in Fedora Core 6 - in Fedora 8 - I blame the new-ness of the libraries it links against (that tarball version doesn't)
Rebuild of Fedora 8 src.rpm in CentOS 5 is also not as stable as the tarball version (I ran tarball version in CentOS 5) but is far more stable than Fedora 8 version in Fedora 8.
Unfortunately I can't use the firefox distributed tarball version because it links against an older libstdc++ which breaks the totem and icedtea plugins.
It would be sweet if upstream firefox would distribute a compiled tarball that links against the newer libstdc++
-
Dan -
Florin Andrei -
J -
Jimmy Bradley -
Mark Weaver -
Max Hetrick -
MHR -
Michael A. Peters -
Nancy Rudins -
Niki Kovacs -
Scott Ehrlich