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