Bug 672139

Summary: [abrt] epiphany-1:2.30.6-1.fc14: memcpy: Process /usr/bin/epiphany was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Paolo Niccolò Giubelli <paoloniccolo.giubelli>
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: i686   
OS: Unspecified   
Whiteboard: abrt_hash:9d324878623b2ec346fa043c302c019cf238b010
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-15 09:29:18 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 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.