Bug 710665

Summary: [abrt] epiphany-1:2.30.6-1.fc14: Process /usr/bin/epiphany was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Ahmed Abdou <mail>
Component: epiphanyAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: gecko-bugs-nobody, rob.townley
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:d142b3b48b3da3c71c76f78380706446d3956f59
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-15 09:33:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Ahmed Abdou 2011-06-03 23:52:08 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 31457 bytes
cmdline: epiphany
component: epiphany
Attached file: coredump, 42328064 bytes
crash_function: WTF::OSAllocator::reserveAndCommit
executable: /usr/bin/epiphany
kernel: 2.6.35.13-91.fc14.x86_64
package: epiphany-1:2.30.6-1.fc14
rating: 4
reason: Process /usr/bin/epiphany was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: 1.Just open it !!!
time: 1307144813
uid: 500
Comment 1 Ahmed Abdou 2011-06-03 23:52:19 UTC 
Created attachment 502929 [details]
File: backtrace
Comment 2 Ahmed Abdou 2011-09-24 07:26:45 UTC 
Package: epiphany-3.0.3-1.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)

Comment
-----
1.Open epiphany.
Comment 3 Martin Stransky 2012-02-15 09:33:04 UTC 
We're using mozilla crash reporter tool which reports crashes directly to mozilla crash database now, ABRT is no longer used for mozilla packages.

This is an automated bug change. If you can reproduce the crash reliably (you have testcase, page where it crashes or so), please reopen this bug and assign it directly to me.

Thanks.