Bug 608285

Summary: [abrt] crash in firefox-3.5.10-1.fc12: Process /usr/lib64/firefox-3.5/firefox was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: punklinux
Component: firefoxAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: drjohnson1, gecko-bugs-nobody
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:ee0861cb072fac52ef199e806ace553c1ffd6069, btparsed
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-09-17 18:01:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
File: backtrace none

Description punklinux 2010-06-26 16:27:09 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/firefox-3.5/firefox
component: firefox
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/firefox-3.5/firefox
global_uuid: ee0861cb072fac52ef199e806ace553c1ffd6069
package: firefox-3.5.10-1.fc12
rating: 4
reason: Process /usr/lib64/firefox-3.5/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
1.running Firefox in background and it crash

Comment 1 punklinux 2010-06-26 16:27:11 UTC
Created attachment 427096 [details]
File: backtrace

Comment 2 d. johnson 2010-09-17 18:01:33 UTC
Thank you for taking the time to report this bug. Updates to this package have been released since it was first reported. If you have time to update the package and re-test, please do so and report the results here. You can obtain the updated package by typing 'yum update' or using the graphical updater, Software Update.

Disable extensions, plugins and non-default themes. Clear cookies and cache. Exit the browser completely.  Then restart the browser and attempt to replicate the crash.

#2  <signal handler called>
No symbol table info available.
#3  GetStyleSVGReset (this=0x7fcd115dd980) at nsStyleStructList.h:151
No locals.
#4  nsStyleContext::GetStyleSVGReset (this=0x7fcd115dd980)
    at nsStyleStructList.h:151
        cachedData = <value optimized out>
#5  0x000000339f1aee43 in GetStyleSVGReset (aFrame=0x7fed115dd4e0)
    at ../../../style/nsStyleStructList.h:151
No locals.
#6  nsSVGIntegrationUtils::UsingEffectsForFrame (aFrame=0x7fed115dd4e0)
    at nsSVGIntegrationUtils.cpp:56
        style = <value optimized out>
#7  0x000000339ee396e9 in nsIFrame::InvalidateInternal (this=0x7fed115dd4e0, 
    aDamageRect=<value optimized out>, aX=<value optimized out>, 
    aY=<value optimized out>, aForChild=<value optimized out>, 
    aFlags=<value optimized out>) at nsFrame.cpp:3739
No locals.
#8  0x000000339ee38409 in nsIFrame::InvalidateInternalAfterResize (
    this=0x7fed115ddd20, aDamageRect=..., aX=0, aY=0, 
    aFlags=<value optimized out>) at nsFrame.cpp:3731
No locals.
#9  0x000000339ee39741 in nsIFrame::InvalidateInternal (this=0x7fed115ddd20, 

Thank you for taking the time to report this bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash, because there are no debugging symbols loaded (probably abrt failed to load them).

Unfortunately, we cannot use this backtrace.


Fedora Bugzappers volunteer triage team