Bug 623114 - [abrt] crash in epiphany-2.30.2-1.fc13: malloc_consolidate: Process /usr/bin/epiphany was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in epiphany-2.30.2-1.fc13: malloc_consolidate: Process /usr/bin/...
Status: CLOSED DUPLICATE of bug 602796
Alias: None
Product: Fedora
Classification: Fedora
Component: epiphany   
(Show other bugs)
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:263415b4a5d3656a277609e434f...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-11 11:29 UTC by Kamil Kulik
Modified: 2010-11-09 15:25 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-11-09 15:25:52 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (45.99 KB, text/plain)
2010-08-11 11:29 UTC, Kamil Kulik 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Kamil Kulik 2010-08-11 11:29:01 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: epiphany
component: epiphany
crash_function: malloc_consolidate
executable: /usr/bin/epiphany
global_uuid: 263415b4a5d3656a277609e434f8d7287ab633b9
kernel: 2.6.33.6-147.2.4.fc13.x86_64
package: epiphany-2.30.2-1.fc13
rating: 4
reason: Process /usr/bin/epiphany was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1.trying to connect to shttp site
2.
3.
Comment 1 Kamil Kulik 2010-08-11 11:29:05 UTC 
Created attachment 438163 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 15:25:52 UTC 

*** This bug has been marked as a duplicate of bug 602796 ***
Comment 3 Karel Klíč 2010-11-09 15:25:52 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #602796.

Sorry for the inconvenience.
Note You need to log in before you can comment on or make changes to this bug.