Bug 672139 - [abrt] epiphany-1:2.30.6-1.fc14: memcpy: Process /usr/bin/epiphany was killed by signal 11 (SIGSEGV)
Summary: [abrt] epiphany-1:2.30.6-1.fc14: memcpy: Process /usr/bin/epiphany was killed...
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:9d324878623b2ec346fa043c302...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-24 07:09 UTC by Paolo Niccolò Giubelli
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:18 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (68.27 KB, text/plain)
2011-01-24 07:09 UTC, Paolo Niccolò Giubelli
no flags Details

Description Paolo Niccolò Giubelli 2011-01-24 07:09:43 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: epiphany
component: epiphany
crash_function: memcpy
executable: /usr/bin/epiphany
kernel: 2.6.35.10-74.fc14.i686
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: 1295852362
uid: 500

How to reproduce
-----
1. Browsing into wordpress wp-admin
2. Opening another tab in google analytics
3.

Comment 1 Paolo Niccolò Giubelli 2011-01-24 07:09:48 UTC
Created attachment 474900 [details]
File: backtrace

Comment 2 Paolo Niccolò Giubelli 2011-02-25 20:54:22 UTC
Package: epiphany-1:2.30.6-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
I opened google analytics

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