Kevin J. Cummings cummings at
Wed Jul 14 20:46:09 UTC 2010

On 07/14/2010 04:33 PM, Marcel Rieux wrote:
> Firefox is often killed by signal 11:
> Package:        firefox-3.5.10-1.fc12
> Latest Crash:    Mon 12 Jul 2010 11:45:16 PM
> Command:        /usr/lib64/firefox-3.5/firefox --sm-config-prefix
> /firefox-P8PZv6/ --sm-client-id
> 10a7781fec216fecbb127887078888787700000015530047 --screen 0
> Reason:         Process /usr/lib64/firefox-3.5/firefox was killed by
> signal 11 (SIGSEGV)
> Comment:        None
> Bug Reports:   
> Today, abrt even reported a kernel crash... with no detail:
> Package:        kernel
> Latest Crash:    Tue 13 Jul 2010 09:29:07 PM
> Command:        not_applicable
> Reason:         ------------[ cut here ]------------
> Comment:        None
> Bug Reports:   
> But the system stayed stable. Is this any cause for concern. Is this
> really the kind of stuff that should be reported? I wonder if, for
> know-nothing liek me, abrt is more than a nuisance.

If you are absolutely sure that the program in question is good, then
SIG11 probably means you have a hardware problem.  In this case, it
could be a RAM problem, either a bad RAM stick, or one that fails under
stress, and firefox can certainly be stressful when it wants to be.  B^)
It could be a motherboard problem related you your memory subsystem.
It could be lots of things, mostly hardware related.

Just because the "system" stayed stable, doesn't mean you have no
problem at all.  It just means that running firefox helps bring it to
the forefront.

Have you read the (somewhat dated) FAQ here:

Kevin J. Cummings
kjchome at
cummings at
cummings at
Registered Linux User #1232 (

More information about the users mailing list