[opensuse] seamonkey randomly crashing on 10.3
Hello, Because of the nature of my work I use both Seamonkey and FireFox (and sometimes Konqeror) all at the same time. On SuSE 10.2 Seamonkey was very stable, I never had problems with it. I'm pretty sure I had upgraded seamonkey to 1.1.7 (latest) while still on 10.2. Recently I've done a fresh reinstall with openSuSE10.3 and Seamonkey is pretty unstable. The worse part is that it's unpredictable and I can't find the source of the crash. I've been running it from a terminal window hoping to catch an informative error but I don't get much. Sessions always look more or less like this: :>seamonkey Flash Player: Warning: environment variable G_FILENAME_ENCODING is set and is not UTF-8 Flash Player: Warning: environment variable G_FILENAME_ENCODING is set and is not UTF-8 Flash Player: Warning: environment variable G_FILENAME_ENCODING is set and is not UTF-8 Flash Player: Warning: environment variable G_FILENAME_ENCODING is set and is not UTF-8 Flash Player: Warning: environment variable G_FILENAME_ENCODING is set and is not UTF-8 /usr/bin/seamonkey: line 277: 26823 Segmentation fault $AOSS $MOZ_PROGRAM $MOZ_LANG Sometimes it will run for a week and a half before crashing. Sometimes for a couple days. Sometimes for 20 minutes. It does not seem to be any particular site or action that causes it to crash. FireFox is not having any of these problems. Has anyone experience this sort of thing? It was crashing as soon as I installed of the DVD, before I installed any updates, or third party things. I have since upgraded to the lastest security update with YOU, and it's just the same. I've also added the latest flash and acroread from packman, but that does not seem to have made the situation better or worse either. Is anyone else having these problems? How can I debug this? JW -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hello,
Because of the nature of my work I use both Seamonkey and FireFox (and sometimes Konqeror) all at the same time. On SuSE 10.2 Seamonkey was very stable, I never had problems with it. I'm pretty sure I had upgraded seamonkey to 1.1.7 (latest) while still on 10.2.
Recently I've done a fresh reinstall with openSuSE10.3 and Seamonkey is pretty unstable. The worse part is that it's unpredictable and I can't find the source of the crash.
I've been running it from a terminal window hoping to catch an informative
error but I don't get much. Sessions always look more or less like
On Tuesday 05 February 2008, Jonathan Wilson wrote: this:
:>seamonkey
Flash Player: Warning: environment variable G_FILENAME_ENCODING is set and is not UTF-8 Flash Player: Warning: environment variable G_FILENAME_ENCODING is set and is not UTF-8 Flash Player: Warning: environment variable G_FILENAME_ENCODING is set and is not UTF-8 Flash Player: Warning: environment variable G_FILENAME_ENCODING is set and is not UTF-8 Flash Player: Warning: environment variable G_FILENAME_ENCODING is set and is not UTF-8 /usr/bin/seamonkey: line 277: 26823 Segmentation fault $AOSS $MOZ_PROGRAM $MOZ_LANG
Sometimes it will run for a week and a half before crashing. Sometimes for a couple days. Sometimes for 20 minutes. It does not seem to be any particular site or action that causes it to crash.
FireFox is not having any of these problems.
Has anyone experience this sort of thing? It was crashing as soon as I installed of the DVD, before I installed any updates, or third party things. I have since upgraded to the lastest security update with YOU, and it's just the same. I've also added the latest flash and acroread from packman, but that does not seem to have made the situation better or worse either.
Is anyone else having these problems? How can I debug this?
On my 10.3, Seamonkey Composer is anything but stable. Once it crashes (the program window simply disappears), Firefox, too, becomes unstable and will sooner or later similarly just disappear in the thin air, with no crash dialogue, or that wizard thing that normally follows when some poor AJAXed site crashes it. To avoid this, once Seamonkey has crashed, I have to kill gconfd-2 and restart Firefox and Seamonkey. Things are then back to normal. Either Seamonkey screws up gconfd-2, or vice versa. Either way, unless I kill gconfd-2 after the Seamonkey 1.1.7 crash, GTK apps will become unstable. I now try to use Seamonkey as little as possible. Regards, Tero Pesonen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jonathan Wilson wrote:
Hello,
Because of the nature of my work I use both Seamonkey and FireFox (and sometimes Konqeror) all at the same time. On SuSE 10.2 Seamonkey was very stable, I never had problems with it. I'm pretty sure I had upgraded seamonkey to 1.1.7 (latest) while still on 10.2.
The last 18 months worth of seamonkey have been marginally unstable on 10.1. I have reason to believe the Seamonkey has some serious memory leaks.
Recently I've done a fresh reinstall with openSuSE10.3 and Seamonkey is pretty unstable. The worse part is that it's unpredictable and I can't find the source of the crash.
Well, if it's earlier than Seamonkey 1.1.7, its a problem with Seamonkey. Each release has improved, but not yet perfected stability. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Aaron Kulkis wrote:
Jonathan Wilson wrote:
Hello,
Because of the nature of my work I use both Seamonkey and FireFox (and sometimes Konqeror) all at the same time. On SuSE 10.2 Seamonkey was very stable, I never had problems with it. I'm pretty sure I had upgraded seamonkey to 1.1.7 (latest) while still on 10.2.
The last 18 months worth of seamonkey have been marginally unstable on 10.1.
I have reason to believe the Seamonkey has some serious memory leaks.
Recently I've done a fresh reinstall with openSuSE10.3 and Seamonkey is pretty unstable. The worse part is that it's unpredictable and I can't find the source of the crash.
Well, if it's earlier than Seamonkey 1.1.7, its a problem with Seamonkey. Each release has improved, but not yet perfected stability.
Ok, I have to admit that my SeaMonkey does never run longer than approximately 18 hours on 10.3 and I almost never crash with it. And if I do it's almost everytime Flash-nspluginwrapper. And it seems that some package management brings it down sometimes. Could be gconf related as sometimes when I update unrelated packages SeaMonkey is just closing down. But overall stability is quite good here (at least for the 18 hours runtime). If you don't use mailnews for example SM shouldn't have any more memory leaks than Firefox. (Probably a bit because of xpfe but at least Gecko is the same). Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2008-02-06 at 18:05 +0100, Wolfgang Rosenauer wrote:
And it seems that some package management brings it down sometimes. Could be gconf related as sometimes when I update unrelated packages SeaMonkey is just closing down.
I had that this morning, with firefox. I suddenly got a pop up that certain app (name unrelated to anything familiar; could be gecko) had crashed, and it happened while yast was installing something (libqt4-devel). I said "no" to send a report, and then I noticed it was firefox who crashed. Not the first time, either. Next time I'll say yes and fill a bugzilla, if you want it. By the way, when I restarted firefox a while ago, it detected the crash. I said ok to recover the status quo, but one of the three windows is hanged using 15..25% cpu continously, and not managing to load any of the 8 tab, continously shown "loading O" - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHqgWktTMYHG2NR9URAriaAKCQttqoOfFZ1fDlkTISLBg/mKP1ZQCgidZg HvLUKzKLyHfo6vGfrusyyJ0= =mha/ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Wolfgang Rosenauer wrote:
Aaron Kulkis wrote:
Jonathan Wilson wrote:
Hello,
Because of the nature of my work I use both Seamonkey and FireFox (and sometimes Konqeror) all at the same time. On SuSE 10.2 Seamonkey was very stable, I never had problems with it. I'm pretty sure I had upgraded seamonkey to 1.1.7 (latest) while still on 10.2.
The last 18 months worth of seamonkey have been marginally unstable on 10.1.
I have reason to believe the Seamonkey has some serious memory leaks.
Recently I've done a fresh reinstall with openSuSE10.3 and Seamonkey is pretty unstable. The worse part is that it's unpredictable and I can't find the source of the crash.
Well, if it's earlier than Seamonkey 1.1.7, its a problem with Seamonkey. Each release has improved, but not yet perfected stability.
Ok, I have to admit that my SeaMonkey does never run longer than approximately 18 hours on 10.3 and I almost never crash with it. And if I do it's almost everytime Flash-nspluginwrapper. And it seems that some package management brings it down sometimes. Could be gconf related as sometimes when I update unrelated packages SeaMonkey is just closing down. But overall stability is quite good here (at least for the 18 hours runtime). If you don't use mailnews for example SM shouldn't have any more memory leaks than Firefox. (Probably a bit because of xpfe but at least Gecko is the same).
Most of my SeaMonkey instability seems to be related to the mail/news-reader portion And this is on a 10.1 machine with the original kernel. (I haven't been able to get Y.O.U. to update anything). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Aaron Kulkis a écrit :
Most of my SeaMonkey instability seems to be related to the mail/news-reader portion
surprising. I use it all the time without problem. Crash happen with videos (probably flash player) and some web pages (undefined) given this I use dayly build (changed once in a while), that is V2, for some time, now jdd -- http://www.dodin.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2008-02-06 at 22:43 -0500, Aaron Kulkis wrote:
And this is on a 10.1 machine with the original kernel. (I haven't been able to get Y.O.U. to update anything).
Why? :-o - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHq2PEtTMYHG2NR9URAucvAJwPzdxH4vgxbz6bKZor5XtP9dSknwCgjBr7 BuMJU6GDEHWp5m4EVGZqnSY= =j0Wt -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jonathan Wilson wrote:
Has anyone experience this sort of thing?
Yes. Very frequent crashes (2 or 3 times per week) and corrupted websites with the Suse(!) version of Seamonkey, see bug 332112 [1]. That bug has been open for quite a while now. I installed the original binaries from [2], they work. Well, no flash support out of the box, but at least this way you do not need to install Flashblock ;) Regards nordi [1] https://bugzilla.novell.com/show_bug.cgi?id=332112 [2] http://www.seamonkey-project.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
nordi wrote:
Jonathan Wilson wrote:
Has anyone experience this sort of thing?
Yes. Very frequent crashes (2 or 3 times per week) and corrupted websites with the Suse(!) version of Seamonkey, see bug 332112 [1]. That bug has been open for quite a while now.
I'm using SeaMonkey all the time and interestingly I never ever saw this behaviour myself. That is a really weird issue and I also see no real reason what patch could ever influence the html source/cache behaviour at all :-( Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 06 February 2008 18:19:28 nordi wrote:
Jonathan Wilson wrote:
Has anyone experience this sort of thing?
Yes. Very frequent crashes (2 or 3 times per week) and corrupted websites with the Suse(!) version of Seamonkey, see bug 332112 [1]. That bug has been open for quite a while now.
I installed the original binaries from [2], they work. Well, no flash support out of the box, but at least this way you do not need to install Flashblock ;)
Regards nordi
[1] https://bugzilla.novell.com/show_bug.cgi?id=332112 [2] http://www.seamonkey-project.org
Thanks for all the input, folks. Though I'm not sure I'm experiencing the same bug mentioned at [1], because I don't have rendering problems, it just crashes. I think I might try rebuilding the source rpm and see if it's any better. It does not seem to have anything to do with flash or any specific site. As I mentioned, what bothers me the most is it's unpredictable. JW -- ---------------------- System Administrator - Cedar Creek Software http://www.cedarcreeksoftware.com http://jwadmin.blogspot.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (7)
-
Aaron Kulkis -
Carlos E. R. -
jdd -
Jonathan Wilson -
nordi -
Tero Pesonen -
Wolfgang Rosenauer