Bug 701052

Summary: [abrt] epiphany-1:2.30.6-1.fc14: Process /usr/bin/epiphany was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Scott <geekboy>
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:3d4fbbbeddd1726aed2159c57cd84d99e1b42ada
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-15 09:29:41 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 Scott 2011-04-30 16:46:44 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 76208 bytes
cmdline: epiphany
component: epiphany
Attached file: coredump, 2463166464 bytes
crash_function: lookup<WebCore::FontData const*, WTF::IdentityHashTranslator<WebCore::FontData const*, std::pair<WebCore::FontData const*, WebCore::GlyphPageTreeNode*>, WTF::PtrHash<WebCore::FontData const*> > >
executable: /usr/bin/epiphany
kernel: 2.6.35.12-90.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: 1304181763
uid: 1000

How to reproduce
-----
1.Lauch Browser
2.Open several pages (each in their own tab.
3.Switch from one tab to another.
Comment 1 Scott 2011-04-30 16:46:46 UTC 
Created attachment 495981 [details]
File: backtrace
Comment 2 Martin Stransky 2012-02-15 09:29:41 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.