Have you recently upgraded your system from one OS to another? Have you added some libraries (/usr/local/lib or /opt/lib) to your system recently? Thanks, LDB On Mon, 12 Sep 2005 09:25:52 -0600, Darryl Gregorash wrote

Almost since version 1.0, I've been plagued with Mozilla crashing due to a SEGV, but I have been unable to track it down (it would be nice to have a Talkback-enabled version in the distro, guys). The only error message anywhere is in .X.err, which simply says that mozilla-bin crashed due to a segmentation fault. There is no pattern to the crashes -- it will crash running unattended, it will crash on almost any URL, all apparently at random. The unattended crashes suggest to me that the problem exists somewhere in common code, not just in the browser itself (all that should be happening unattended is email checks).

Previously, it hasn't been so bothersome that I was prepared to go digging to find it (maybe I hoped it would just disappear in the next release :) ), but now... sometimes, when I try to reload, I get 3 or 4, or more, consecutive crashes on the same URL before it will load. Clearing the cache does not seem to help.

For now, I don't want to speculate -- all I am looking for is some way to track this thing down. Searching bugzilla at mozilla.org was useless, an internet-wide google search for "mozilla segmentation.fault" produced 172,000 even more useless results (at least, they are more useless if the first 5 are any indication), and the SuSE database is silent on the issue. The only useful bit of information I have found is that there has been a SEGV problem in all Mozilla (and maybe Thunderbird) releases since day 1, and it has not gone away -- well, I already knew that anyway.

I have installed the mozilla-debuginfo package, and I have found a shell script /opt/mozilla/lib/run-mozilla.sh (part of the mozilla package) which seems to allow the binary to be run from a debugger. Is this sufficient to try to track down the bug? If not, what else do I need? (Yes, I have the debugger installed!! :) ) I really do not feel like downloading and compiling a Talkback-enabled version, if I do not have to.

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

Almost since version 1.0, I've been plagued with Mozilla crashing due to a SEGV, but I have been unable to track it down (it would be nice to have a Talkback-enabled version in the distro, guys). The only error message anywhere is in .X.err, which simply says that mozilla-bin crashed due to a segmentation fault. There is no pattern to the crashes -- it will crash running unattended, it will crash on almost any URL, all apparently at random. The unattended crashes suggest to me that

problem exists somewhere in common code, not just in the browser itself (all that should be happening unattended is email checks).

Previously, it hasn't been so bothersome that I was prepared to go digging to find it (maybe I hoped it would just disappear in the next release :) ), but now... sometimes, when I try to reload, I get 3 or 4, or more, consecutive crashes on the same URL before it will load. Clearing the cache does not seem to help.

For now, I don't want to speculate -- all I am looking for is some way to track this thing down. Searching bugzilla at mozilla.org was useless, an internet-wide google search for "mozilla segmentation.fault"

172,000 even more useless results (at least, they are more useless if the first 5 are any indication), and the SuSE database is silent on

Hi, I had the some problem for a while (it is probably gtk-related problem which also have affected NVU). Upgrading to the latest gnome components from SuSE ftp solved this problem. ************************************************ ***   with best regards ***   Andrei Verovski (aka MacGuru) ***   Mac, Linux, DTP, Programming Web Site *** ***   http://snow.prohosting.com/guru4mac/ ************************************************ On Monday 12 September 2005 18:25, Darryl Gregorash wrote: the produced the

issue. The only useful bit of information I have found is that there has been a SEGV problem in all Mozilla (and maybe Thunderbird) releases since day 1, and it has not gone away -- well, I already knew that anyway.

I have installed the mozilla-debuginfo package, and I have found a shell script /opt/mozilla/lib/run-mozilla.sh (part of the mozilla package) which seems to allow the binary to be run from a debugger. Is this sufficient to try to track down the bug? If not, what else do I need? (Yes, I have the debugger installed!! :) ) I really do not feel like downloading and compiling a Talkback-enabled version, if I do not have to.