Bug 593916 - [abrt] crash in epiphany-2.30.2-1.fc13: frame: Process /usr/bin/epiphany was killed by signal 11 (SIGSEGV)
[abrt] crash in epiphany-2.30.2-1.fc13: frame: Process /usr/bin/epiphany was ...
Status: CLOSED DUPLICATE of bug 593151
Product: Fedora
Classification: Fedora
Component: epiphany (Show other bugs)
13
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Gecko Maintainer
Fedora Extras Quality Assurance
abrt_hash:c032b320eaea0eb9c7d2a3e72da...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-19 23:50 EDT by Iván Jiménez
Modified: 2010-05-25 05:47 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-25 05:47:29 EDT
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 (46.35 KB, text/plain)
2010-05-19 23:50 EDT, Iván Jiménez
no flags Details

  None (edit)
Description Iván Jiménez 2010-05-19 23:50:29 EDT
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: epiphany
comment: I had fsf.org in one window and git.gome.org in other, the i hit back on the later and epiphany froze for about 2 s and the crashed.
component: epiphany
crash_function: frame
executable: /usr/bin/epiphany
global_uuid: c032b320eaea0eb9c7d2a3e72da06e280936fca8
kernel: 2.6.33.4-95.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
-----
Not sure, but every crash i've seen was after clicking back. Unfortunatley if I recover my session and hit back, I can't reproduce it
Comment 1 Iván Jiménez 2010-05-19 23:50:32 EDT
Created attachment 415306 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 05:47:29 EDT

*** This bug has been marked as a duplicate of bug 593151 ***
Comment 3 Karel Klíč 2010-05-25 05:47:29 EDT
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 #593151.

Sorry for the inconvenience.

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