Firefox 1.0 segmentation fault
 

I am having some trouble with firefox 1.0. When I open certain links firefox crashes. showing this error message:

/usr/local/firefox/run-mozilla.sh: line 159: 8878 Segmentation fault "$prog" ${1+"$@"}

The underlined number varies. I can reproduce the fault every time. It occurs both as root and as normal user. A site I tried visit was (among other):

emboss.bioinformatics.nl

I've read somewere that segmentations fault could have something to do with faulty DIMM'S. However the fault still occurs even when I installed some brandnew DIMM'S.

I'm running Slackware 10.0/current with x.org 6.7.0.

Does anyone know what this message means and/or how I can solve it?

Just an IDEA: Did you try with a fresh clean .mozilla profile? Either delete or rename the current mozilla profile and try again. Sometimes corrupt parts in the profile cause crashes or you may have installed some extension it doesn't like or is incompatible with 1.0.

I deleted my .mozilla directory and it didn't work. I removed my profile using the profilemanager and that didn't work either.

I'm beginning to think I'm the only one experiencing these crashes :cry:

You are not the only one with Firefox grief. My copy, having run on an earlier release pretty much flawlessly bombed on vs 1.0 Some sites would load, others wouldn't, some links would work, others not. Mostly it just totally crashed out and diasppeared up its own backside.

I tried the profile thing but no joy.

I reinstalled but no joy.

I decided that it was some sort of conflict with whatever else I'm running and that if the Firefox guys couldn't produce a browser that ran under all circumstances I'd go find something else (Konqueror, Galeon & Netscape continues to work just fine...I think even Mozilla continued to run fine.

In the end I just downloaded Opera and I have to say that it ROCKS. Plugins happen seemlessly, pages load quickly and it just doesn't crash. I can see why it is about the only browser that people pay for - if you want to lose the tiny adds at the top of the page.

Do yourself a favour, junk Firefox and dl Opera.

That said, the windows version that gets occasional usage on my dualboot laptop and the dozen or so instances I've installed on other M$ machines have all been very good indeed - go figure :-)

BUMP

me too
 

I've been having many crashes with Firefox 1.0, while I had virtually no problems with 0.8 and 0.9x versions!

I dunno what happened to Firefox... I'll just keep sending in the crash reports and hopefully 1.1 or whatever will be better.

Just an observation... I've been using my own Firefox builds for goodness knows how long. I did notice occassional crashes on the binaries built from the official 1.0 release. In the meantime, I've been mainly building from the development tree, which will be the basis for the upcoming 1.1 release. I've noticed the development tree has been getting more and more stable lately so I'd expect 1.1 to be fairly good, if not perfect.

try mozilla-firefox -ProfileManager and try adding new profile for yourself. This seems to solve the segment fault problem caused from messed up profile files from older versions of firefox.

I had a similar problem (same error message, Firefox crashing at some sites) few days ago. I figured it only happened at web sites using the font Helvetica and had something to do with the Freetype libraries and anti-aliasing. What, exactly, I'm not sure.
I fixed it by upgrading the X server to slackware-current (6.8.1) and then building Freetype 2.1.9.

You could always try creating a HTML file for testing, and throw in a "font face='Helvetica'" to quickly test it.

have you submitted a bug to bugzilla?
 

Right.
It crashs when firefox requests /usr/X11R6/lib/X11/fonts/75dpi/helvR12-ISO8859-1.pcf.gz
from fontconfig(perhaps).
To avoid this I removed all dirs with bitmap fonts from /usr/share/fonts - I had a some symlinks to
/usr/X11R6/lib/X11/fonts/... there.
Now it works.
I have to note - it crashed before, even if there's no explicit notification of helvetica font - in ftp:// listings for instance
and at http://fftv.sourceforge.net/ for example.
So, perhaps, it maybe a problem with fontconfig+bitmap fonts ?

I've been getting the same segmentation faults with firefox. Sometimes by retyping the command in the terminal after the seg fault firefox will start right up. This is on a fresh install of Mandrake 10.2 beta updated with cooker so I know I'm running some risks there. I've tried deleting the mozilla profile directory and it didn't seem to do anything.

I just noticed that instead of using the ffremote command to start firefox (the command used by the icon from the gnome menu) but using mozilla-firefox it no longer crashes. For whatever that's worth.

When it crashed I ran it via self-made icon calling .../firefox, not from gnome menu.