I sent a bug report to Mozilla about this, but I was hoping someone here might have an insight on this.
I use SeaMonkey as my default browser (32-bit even though I'm running x86_64 CentOS 5.1), version 1.1.7.
Shortyl after installing 1.1.7 on my 5.0 (and even since 5.1), I noticed that every so often, seemingly at random, although it appears most frequently when I click on something that wants to interact with the file system, the SeaMonkey window just closes. If I reopen it and go to the same place and try the same thing, it works just fine (and usually, the second SM window is more stable and doesn't do that again).
This frequently happens when I try to save a web page, load an email attachment, print a page, or anything that interacts with the file system. Just now it happened when I tried to switch tabs, but that's unusual.
Anyone have a clue?
TIA.
mhr
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
MHR wrote:
I sent a bug report to Mozilla about this, but I was hoping someone here might have an insight on this.
I use SeaMonkey as my default browser (32-bit even though I'm running x86_64 CentOS 5.1), version 1.1.7.
Shortyl after installing 1.1.7 on my 5.0 (and even since 5.1), I noticed that every so often, seemingly at random, although it appears most frequently when I click on something that wants to interact with the file system, the SeaMonkey window just closes. If I reopen it and go to the same place and try the same thing, it works just fine (and usually, the second SM window is more stable and doesn't do that again).
This frequently happens when I try to save a web page, load an email attachment, print a page, or anything that interacts with the file system. Just now it happened when I tried to switch tabs, but that's unusual.
Anyone have a clue?
I've been having this happen on Firefox the last week or two since I loaded CentOS 5.1 on my laptop, on just a plain old 32 bit system.
firefox-1.5.0.12-7.el5.centos
I thought it was perhaps one of my plugins I have installed, so I've just been dealing with it because I haven't had time to check it out. Mine is doing exactly the same thing.
Regards, Max
On Mon, Jan 07, 2008 at 08:17:00PM -0500, Max Hetrick wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
MHR wrote:
I sent a bug report to Mozilla about this, but I was hoping someone here might have an insight on this.
I use SeaMonkey as my default browser (32-bit even though I'm running x86_64 CentOS 5.1), version 1.1.7.
Shortyl after installing 1.1.7 on my 5.0 (and even since 5.1), I noticed that every so often, seemingly at random, although it appears most frequently when I click on something that wants to interact with the file system, the SeaMonkey window just closes. If I reopen it and go to the same place and try the same thing, it works just fine (and usually, the second SM window is more stable and doesn't do that again).
This frequently happens when I try to save a web page, load an email attachment, print a page, or anything that interacts with the file system. Just now it happened when I tried to switch tabs, but that's unusual.
Anyone have a clue?
I've been having this happen on Firefox the last week or two since I loaded CentOS 5.1 on my laptop, on just a plain old 32 bit system.
firefox-1.5.0.12-7.el5.centos
I thought it was perhaps one of my plugins I have installed, so I've just been dealing with it because I haven't had time to check it out. Mine is doing exactly the same thing.
Firefox does this to me quite frequently, and it always has. every new release they say they've improved the stability, but it hasn't made any improvement for me in terms of this issue.
I recently downloaded the firefox source and did my own build, just to see if the failures might have been due to some small incompatibility between the target system the official binaries are built for, and my box. Sad to say that while it may not die as often, it still does it.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
fred smith wrote:
Firefox does this to me quite frequently, and it always has. every new release they say they've improved the stability, but it hasn't made any improvement for me in terms of this issue.
I've never had Firefox do this before.
Max
fred smith wrote:
Firefox does this to me quite frequently, and it always has. every new release they say they've improved the stability, but it hasn't made any improvement for me in terms of this issue.
I recently downloaded the firefox source and did my own build, just to see if the failures might have been due to some small incompatibility between the target system the official binaries are built for, and my box. Sad to say that while it may not die as often, it still does it.
This doesn't answer the original poster's question, but....
As far as Firefox is concerned you might want to try giving 3.0b2 a try. I found it to be significantly more stable than the 1.5.X branch under Winders and on various Macs (haven't gotten around to trying it on a CentOS 5.X desktop box yet).
Best,
On Mon, Jan 07, 2008 at 08:31:33PM -0500, Chris Mauritz wrote:
fred smith wrote:
Firefox does this to me quite frequently, and it always has. every new release they say they've improved the stability, but it hasn't made any improvement for me in terms of this issue.
I recently downloaded the firefox source and did my own build, just to see if the failures might have been due to some small incompatibility between the target system the official binaries are built for, and my box. Sad to say that while it may not die as often, it still does it.
This doesn't answer the original poster's question, but....
As far as Firefox is concerned you might want to try giving 3.0b2 a try. I found it to be significantly more stable than the 1.5.X branch under Winders and on various Macs (haven't gotten around to trying it on a CentOS 5.X desktop box yet).
Hey Chris, a blast from the past (remember the old Coherent newsgroups??)
Well, From 1.0, or perhaps even earlier, up thru 2.0.whatever-todays-release is I've always had that issue. It's largely nothing more than a modest irritant since I can reopen the same page(s)/window(s) I had open before the crash.
I'll probably take a look at version 3 one of these days, thanks for reminding me.
Fred
fred smith wrote:
Firefox does this to me quite frequently, and it always has. every new release they say they've improved the stability, but it hasn't made any improvement for me in terms of this issue.
Firefox 2 works fine for me on Ubuntu 7.10, Ubuntu 7.04, Fedora 7 and Windows XP.
MHR wrote:
I sent a bug report to Mozilla about this, but I was hoping someone here might have an insight on this.
I use SeaMonkey as my default browser (32-bit even though I'm running x86_64 CentOS 5.1), version 1.1.7.
Shortyl after installing 1.1.7 on my 5.0 (and even since 5.1), I noticed that every so often, seemingly at random, although it appears most frequently when I click on something that wants to interact with the file system, the SeaMonkey window just closes.
you mean seamonkey crashes, right? ie, all other seamonkey windows on the box close? I've been seeing that at home on a 32-bit centos 5 system... very annoying! But I haven't noticed it on my 64-bit machine at work, where I use an x86_64 seamonkey (with nspluginwrapper for flash), straight rebuild of seamonkey-1.1.7-1.fc7.src.rpm.
You might want to try that.
On Jan 8, 2008 12:33 AM, Nicolas Thierry-Mieg Nicolas.Thierry-Mieg@imag.fr wrote:
you mean seamonkey crashes, right? ie, all other seamonkey windows on the box close?
Can't say - I use the tabs and rarely ever have more than one SM window open.
I've been seeing that at home on a 32-bit centos 5 system... very
annoying!
But I haven't noticed it on my 64-bit machine at work, where I use an x86_64 seamonkey (with nspluginwrapper for flash), straight rebuild of seamonkey-1.1.7-1.fc7.src.rpm.
You might want to try that.
I've never been able to get the nspluginwrapper to work reliably for me, which is why I run the 32-bit version of SM.
However, I have been asked by the Mozilla folks to run their L&G nightly built (alpha) version, which I am at the moment, and so far so good. Hopefully this will crash at some point and produce a report/dump/log/whatever that they can use to isolate the problem.
In the mean time, who knows? It only bites about once a day, at random, usually at the worst possible moment.
I'll post whatever results I find, hopefully soon and good.
Thanks.
mhr
Shortyl after installing 1.1.7 on my 5.0 (and even since 5.1), I noticed that every so often, seemingly at random, although it appears most frequently when I click on something that wants
I have also experienced this problem and characterized it briefly by unscientific trial and error (FWIW). I found that whenever it dies it is trying to open a new window per javascript ALERT or CONFIRM directives. This happens intermittently and NONrepeatably on both 32 and 64 bit flavours of 5.1 and no other js commands seem to be related (including whether a flash file is or is not being displayed). This started late last year. It was not so much of a nusiance that I bothered to see what updates coincided with it then and I would just be guessing if I looked back now.
The problem seems to lie in the code by which FF/SM open windows in those two javascript commands. I run Adblock, noscript, NViIDIA's proprietary drivers, kde and permissive selinux. Nothing of interest appears in /var/log/<anything> or dmesg coincident with the failure.
regards,
benm
On Jan 8, 2008 9:58 AM, Ben Mohilef benm@dsl-only.net wrote:
Shortyl after installing 1.1.7 on my 5.0 (and even since 5.1), I noticed that every so often, seemingly at random, although it appears most frequently when I click on something that wants
I have also experienced this problem and characterized it briefly by unscientific trial and error (FWIW). I found that whenever it dies it is
trying
to open a new window per javascript ALERT or CONFIRM directives. This happens intermittently and NONrepeatably on both 32 and 64 bit flavours of 5.1 and no other js commands seem to be related (including whether a flash file is or is not being displayed). This started late last year. It
was not
so much of a nusiance that I bothered to see what updates coincided with
it
then and I would just be guessing if I looked back now.
The problem seems to lie in the code by which FF/SM open windows in those two javascript commands. I run Adblock, noscript, NViIDIA's proprietary drivers, kde and permissive selinux. Nothing of interest
appears
in /var/log/<anything> or dmesg coincident with the failure.
Interesting - that might explain it, but only if SM uses JS to create its local Save To File or other input windows, which I couldn't say (never looked at the source).
I'll keep that in mind.
Thanks.
mhr
MHR wrote:
On Jan 8, 2008 9:58 AM, Ben Mohilef benm@dsl-only.net wrote:
Shortyl after installing 1.1.7 on my 5.0 (and even since 5.1), I noticed that every so often, seemingly at random, although it appears most frequently when I click on something that wants
I have also experienced this problem and characterized it briefly by unscientific trial and error (FWIW). I found that whenever it dies it is
trying
to open a new window per javascript ALERT or CONFIRM directives. This happens intermittently and NONrepeatably on both 32 and 64 bit flavours of 5.1 and no other js commands seem to be related (including whether a flash file is or is not being displayed). This started late last year. It
was not
so much of a nusiance that I bothered to see what updates coincided with
it
then and I would just be guessing if I looked back now.
The problem seems to lie in the code by which FF/SM open windows in those two javascript commands. I run Adblock, noscript, NViIDIA's proprietary drivers, kde and permissive selinux. Nothing of interest
appears
in /var/log/<anything> or dmesg coincident with the failure.
Interesting - that might explain it, but only if SM uses JS to create its local Save To File or other input windows, which I couldn't say (never looked at the source).
I'll keep that in mind.
Also, it has been my experience that a messed up profile (especially after an upgrade) can cause problems.
You can test this by moving the ~/.mozilla to ~/.mozilla_bak and see if still have issues. This will remove all your bookmarks, etc ... but you can move them back later on if this does not increase stability by moving .mozilla_bak back to .mozilla.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Johnny Hughes wrote:
Also, it has been my experience that a messed up profile (especially after an upgrade) can cause problems.
You can test this by moving the ~/.mozilla to ~/.mozilla_bak and see if still have issues. This will remove all your bookmarks, etc ... but you can move them back later on if this does not increase stability by moving .mozilla_bak back to .mozilla.
Johnny,
I just followed your advice and moved my profile over to create a new one. I copied my bookmarks over and reloaded my plugins manually. I'll post if this resolved my issues.
Perhaps others can try this then approach then. Thanks for the tip!
Regards, Max
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Max Hetrick wrote:
I just followed your advice and moved my profile over to create a new one. I copied my bookmarks over and reloaded my plugins manually. I'll post if this resolved my issues.
After following Johnny's advice, I moved my old profile over to the side and allowed Firefox to create a new one. I then installed the plugins I use manually fresh, and also copied my bookmarks.html file back over. I also use a different theme and installed that fresh.
I've been running it now all day long with 8 tabs going on one page like I do everyday. The other page is open with at least a few tabs going. I use this page as my browsing/searching page and the other as my work related page.
Since doing this last evening, I have not had Firefox crash even once today. Perhaps everyone else having issues could try this solution to fix their problems.
Regards, Max
On Jan 9, 2008 1:54 PM, Max Hetrick maxhetrick@verizon.net wrote:
After following Johnny's advice, I moved my old profile over to the side and allowed Firefox to create a new one. I then installed the plugins I use manually fresh, and also copied my bookmarks.html file back over. I also use a different theme and installed that fresh.
I've been running it now all day long with 8 tabs going on one page like I do everyday. The other page is open with at least a few tabs going. I use this page as my browsing/searching page and the other as my work related page.
Since doing this last evening, I have not had Firefox crash even once today. Perhaps everyone else having issues could try this solution to fix their problems.
Interesting. At the time I read Johnny's post, I was running the 2.0 alpha trunk build of SeaMonkey, and I didn't have any problems at all. One of the things this did when I installed it was to create a new profile and copy over (some of) my settings from the standard installation.
At this time I am running the standard SM and haven't seen a problem since I started it up, but who knows. The profile idea seems pretty good so far.
mhr
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
MHR wrote:
Interesting. At the time I read Johnny's post, I was running the 2.0 alpha trunk build of SeaMonkey, and I didn't have any problems at all. One of the things this did when I installed it was to create a new profile and copy over (some of) my settings from the standard installation.
At this time I am running the standard SM and haven't seen a problem since I started it up, but who knows. The profile idea seems pretty good so far.
Well, I spoke too soon. Firefox has been crashing on me this morning, twice now, since wiping my profile and starting from a fresh one. Again, it was when I went to print something, which brings up the print window.
Regards, Max
On 7 Jan 2008, at 15:46, MHR wrote:
I sent a bug report to Mozilla about this, but I was hoping someone here might have an insight on this.
I use SeaMonkey as my default browser (32-bit even though I'm running x86_64 CentOS 5.1), version 1.1.7.
Shortyl after installing 1.1.7 on my 5.0 (and even since 5.1), I noticed that every so often, seemingly at random, although it appears most frequently when I click on something that wants to interact with the file system, the SeaMonkey window just closes. If I reopen it and go to the same place and try the same thing, it works just fine (and usually, the second SM window is more stable and doesn't do that again).
This frequently happens when I try to save a web page, load an email attachment, print a page, or anything that interacts with the file system. Just now it happened when I tried to switch tabs, but that's unusual.
Anyone have a clue?
TIA.
mhr
Just adding another "me too" to the pot, as I've been experiencing random window disappearances of Firefox 1.5 lately as well (i686). I'm a newcomer to the Red Hat world (lured by SELinux), and during my Debian years I've never had this issue with Firefox/Iceweasel (from 0.9 to 1.5.12), so I'm guessing there has to be something about Re Hat packages.
I was actually thinking it was caused my TabMix Plus extension that I just installed, but seeing this thread makes me believe otherwise...
-- Siraaj Khandkar
Ron Paul - Hope for America http://www.ronpaul2008.com/ http://www.youtube.com/results?search_query=Ron+Paul&search=Search
-
Ben Mohilef -
Chris Mauritz -
Florin Andrei -
fred smith -
Johnny Hughes -
Max Hetrick -
MHR -
Nicolas Thierry-Mieg -
Siraaj Khandkar