Bug 741172 - [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: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:3656d62128c590588081da42f61...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-26 07:04 UTC by mike
Modified: 2012-02-15 09:29 UTC (History)
2 users (show)

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


Attachments (Terms of Use)
File: backtrace (55.66 KB, text/plain)
2011-09-26 07:04 UTC, mike
no flags Details

Description mike 2011-09-26 07:04:42 UTC
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 56993 bytes
cmdline: epiphany
component: epiphany
Attached file: coredump, 196882432 bytes
executable: /usr/bin/epiphany
kernel: 2.6.35.14-96.fc14.i686
package: epiphany-1:2.30.6-1.fc14
rating: 3
reason: Process /usr/bin/epiphany was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1317020412
uid: 500

comment
-----
crashes several second later even after restarting and restoring browsing session

How to reproduce
-----
1. i opened epiphany
2. went to okcupid.com
3. crashes several second later even after restarting and restoring browsing session

Comment 1 mike 2011-09-26 07:04:49 UTC
Created attachment 524841 [details]
File: backtrace

Comment 2 Martin Stransky 2012-02-15 09:29:27 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.