Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 589756 - [abrt] crash in gitg-0.0.5-1.fc12: slab_allocator_free_chunk: Process /usr/bin/gitg was killed by signal 11 (SIGSEGV)
[abrt] crash in gitg-0.0.5-1.fc12: slab_allocator_free_chunk: Process /usr/bi...
Status: CLOSED DUPLICATE of bug 546135
Product: Fedora
Classification: Fedora
Component: gitg (Show other bugs)
12
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Bryan Kearney
Fedora Extras Quality Assurance
abrt_hash:84d56e7b4ce0105693dd82be704...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-06 16:10 EDT by Mathieu Bridon
Modified: 2013-01-10 05:41 EST (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:04:02 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 (24.84 KB, text/plain)
2010-05-06 16:11 EDT, Mathieu Bridon
no flags Details

  None (edit)
Description Mathieu Bridon 2010-05-06 16:10:59 EDT
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: gitg
comment: It happened twice, and each time GitG was working fine while I was using it or the Git command line, but it suddenly crashed while I was doing nothing related to Git (the second time it crashed while I was chatting in IRC with Xchat, not sure what I was doing the first time).
component: gitg
crash_function: slab_allocator_free_chunk
executable: /usr/bin/gitg
global_uuid: 84d56e7b4ce0105693dd82be704dae7da9e3a133
kernel: 2.6.32.11-99.fc12.x86_64
package: gitg-0.0.5-1.fc12
rating: 4
reason: Process /usr/bin/gitg was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. I was using GitG to view my Git tree
2. I was doing some Git-y stuff with the Git command line, and then refreshing GitG to view the new state of my tree
3. GitG crashed after that, while I was not doing anything Git related
Comment 1 Mathieu Bridon 2010-05-06 16:11:02 EDT
Created attachment 412151 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 05:04:02 EDT

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

Sorry for the inconvenience.

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