Bug 693376 - [abrt] epiphany-1:2.30.6-1.fc14: Process /usr/bin/epiphany was killed by signal 11 (SIGSEGV)
Summary: [abrt] epiphany-1:2.30.6-1.fc14: Process /usr/bin/epiphany was killed by sign...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: epiphany
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-04 13:45 UTC by John Kissane
Modified: 2012-02-15 09:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-15 09:30:45 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (173.00 KB, text/plain)
2011-04-04 13:45 UTC, John Kissane 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description John Kissane 2011-04-04 13:45:46 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 177156 bytes
cmdline: epiphany
comment: Opening the URL mentioned crashes it every time.
component: epiphany
Attached file: coredump, 2389835776 bytes
executable: /usr/bin/epiphany
kernel: 2.6.35.11-83.fc14.x86_64
package: epiphany-1:2.30.6-1.fc14
reason: Process /usr/bin/epiphany was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1301924721
uid: 2283

How to reproduce
-----
1. Opened a Garmin connect url - http://connect.garmin.com/activity/76671224
2.
3.
Comment 1 John Kissane 2011-04-04 13:45:49 UTC 
Created attachment 489774 [details]
File: backtrace
Comment 2 Martin Stransky 2012-02-15 09:30:45 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.
Note You need to log in before you can comment on or make changes to this bug.