Segmentation Faults in Mozilla 1.7.5
Hi, Has anyone else who is using Mozilla 1.7.5 been experiencing segmentation faults? The overt symptom is simply that Mozilla disappears. Depending on how you launch it (I use a desktop icon that I created manually to target a "manual" tarball-based installation of Mozilla), there will be a line in you ~/.xsession-errors file like this one: /usr/local/mozilla/run-mozilla.sh: line 451: 15270 Segmentation fault "$prog" ${1+"$@"} I have not been able to discern any pattern or predictability to this symptom. To the best of my recollection, this symptom began with version 1.7.5. It happens infrequently, at most once a day. Here's the build configuration information for the release I'm running: -==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==- about:buildconfig Build platform target i686-pc-linux-gnu Build tools Compiler Version Compiler flags gcc gcc version 3.3.2 (Mandrake Linux 10.0 3.3.2-6mdk) -Wall -W -Wno-unused -Wpointer-arith -Wcast-align -Wno-long-long -pedantic -pthread -pipe c++ gcc version 3.3.2 (Mandrake Linux 10.0 3.3.2-6mdk) -fno-rtti -fno-exceptions -Wall -Wconversion -Wpointer-arith -Wcast-align -Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy -Wno-non-virtual-dtor -Wno-long-long -pedantic -fshort-wchar -pthread -pipe -I/usr/X11R6/include Configure arguments --enable-xft --enable-crypto --disable-tests --disable-debug --enable-optimize=-O2 --enable-default-toolkit=gtk2 --without-system-nspr --without-system-zlib --without-system-jpeg --without-system-png --without-system-mng --enable-crypto -==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==- I'm running SuSE 9.1 with all YOU updates as well as the KDE 3.3.2 "a" supplementary updates. If anyone has any insight into this problem, I'd appreciate hearing it. Thanks. Randall Schulz
Randall R Schulz wrote:
Hi,
Has anyone else who is using Mozilla 1.7.5 been experiencing segmentation faults? The overt symptom is simply that Mozilla disappears. Depending on how you launch it (I use a desktop icon that I created manually to target a "manual" tarball-based installation of Mozilla), there will be a line in you ~/.xsession-errors file like this one:
/usr/local/mozilla/run-mozilla.sh: line 451: 15270 Segmentation fault "$prog" ${1+"$@"}
Actually, it's been doing this at least since 1.4.1, which is the version I am currently running in 9.0. It's also locking up on a seemingly random basis, requiring a "killall -KILL ..." to get rid of it. I haven't encountered a seg fault entry in the X error file in quite some time, but mozilla is still crashing, regularly, frequently (which I define as once a day or more), and unpredictably. I also never did notice any relation between how mozilla was launched, and the presence/absence of such a line, though that doesn't mean there isn't one. FYI, $prog is always $MOZILLA_HOME/mozilla-bin. I doubt this is a KDE problem, or indeed a problem anywhere but in mozilla. Did you compile with Talkback enabled? I'm running the SuSE-supplied version; they always seem to compile with Talkback disabled, so me reporting anything to mozilla.org isn't going to help.
Darryl, On Tuesday 22 February 2005 13:00, Darryl Gregorash wrote:
Randall R Schulz wrote:
Hi,
Has anyone else who is using Mozilla 1.7.5 been experiencing segmentation faults? The overt symptom is simply that Mozilla disappears. Depending on how you launch it (I use a desktop icon that I created manually to target a "manual" tarball-based installation of Mozilla), there will be a line in you ~/.xsession-errors file like this one:
/usr/local/mozilla/run-mozilla.sh: line 451: 15270 Segmentation fault "$prog" ${1+"$@"}
Actually, it's been doing this at least since 1.4.1, which is the version I am currently running in 9.0. It's also locking up on a seemingly random basis, requiring a "killall -KILL ..." to get rid of it.
I haven't encountered a seg fault entry in the X error file in quite some time, but mozilla is still crashing, regularly, frequently (which I define as once a day or more), and unpredictably. I also never did notice any relation between how mozilla was launched, and the presence/absence of such a line, though that doesn't mean there isn't one.
I just meant that there are ways to launch Mozilla that do not direct its standard error to ~/.xsession-error. If KDE does the launching, then unless the program itself redirects its standard out or error, it will end up there. But it's easy to get around this: % mozilla 2>/dev/null is the most trivial example.
FYI, $prog is always $MOZILLA_HOME/mozilla-bin.
Probably, but what I quoted was excerpted from my ~/.xsession-errors file. That's what you'll see there, so that's what I put in my mail.
I doubt this is a KDE problem, or indeed a problem anywhere but in mozilla.
Of course. I never suggested otherwise.
Did you compile with Talkback enabled? I'm running the SuSE-supplied version; they always seem to compile with Talkback disabled, so me reporting anything to mozilla.org isn't going to help.
As I said, I acquired the installation tarball from the Mozilla.org site. I did not compile it myself. Randall Schulz
participants (2)
-
Darryl Gregorash -
Randall R Schulz