Bug 669653

Summary: [abrt] epiphany-1:2.30.6-1.fc14: g_type_check_instance_cast: Process /usr/bin/epiphany was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Anne Ghisla <a.ghisla>
Component: epiphanyAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: gecko-bugs-nobody, rob.townley
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:c2815f52feaa95290925b877262263a8abba9351
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-15 09:31:13 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 Anne Ghisla 2011-01-14 10:20:51 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: epiphany
component: epiphany
crash_function: g_type_check_instance_cast
executable: /usr/bin/epiphany
kernel: 2.6.35.10-74.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: 1295000051
uid: 500

How to reproduce
-----
I was writing a post on my blog on blogspot.com.
When I hit "Publish", epiphany hung a bit and then crashed.

I don't know if it's prerogative of blogspot.com, let me know if I can do more tests.
Comment 1 Anne Ghisla 2011-01-14 10:20:54 UTC 
Created attachment 473495 [details]
File: backtrace
Comment 2 Martin Stransky 2012-02-15 09:31:13 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.