Bug 677204

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, skaturn
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:eeb50fc47ac916f15a026159b7d36d497f4adb7b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-15 09:27:00 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-02-14 02:20:27 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: epiphany
component: epiphany
crash_function: WTF::OSAllocator::reserveAndCommit
executable: /usr/bin/epiphany
kernel: 2.6.35.10-74.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)
time: 1297646949
uid: 500

How to reproduce
-----
1.Just open it
Comment 1 Ahmed Abdou 2011-02-14 02:20:34 UTC 
Created attachment 478536 [details]
File: backtrace
Comment 2 David M. 2011-04-12 02:26:58 UTC 
Package: epiphany-1:2.30.6-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. epiphany crashed on startup
2.
3.


Comment
-----
was running Windows 7 inside VirtualBox concurrently.
Comment 3 Martin Stransky 2012-02-15 09:27:00 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.