Bug 904003 - [abrt] gitg-0.2.5-4.fc18: slab_allocator_free_chunk: Process /usr/bin/gitg was killed by signal 11 (SIGSEGV)
Summary: [abrt] gitg-0.2.5-4.fc18: slab_allocator_free_chunk: Process /usr/bin/gitg wa...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gitg
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ignacio Casal Quinteiro (nacho)
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:fbea41a1e3acce1fd40af765988...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-25 09:16 UTC by Insang Ryu
Modified: 2014-02-05 18:28 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 18:28:50 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (33.20 KB, text/plain)
2013-01-25 09:16 UTC, Insang Ryu
no flags Details
File: cgroup (129 bytes, text/plain)
2013-01-25 09:16 UTC, Insang Ryu
no flags Details
File: core_backtrace (4.81 KB, text/plain)
2013-01-25 09:16 UTC, Insang Ryu
no flags Details
File: dso_list (9.73 KB, text/plain)
2013-01-25 09:16 UTC, Insang Ryu
no flags Details
File: environ (1.56 KB, text/plain)
2013-01-25 09:16 UTC, Insang Ryu
no flags Details
File: limits (1.29 KB, text/plain)
2013-01-25 09:16 UTC, Insang Ryu
no flags Details
File: maps (47.34 KB, text/plain)
2013-01-25 09:16 UTC, Insang Ryu
no flags Details
File: open_fds (784 bytes, text/plain)
2013-01-25 09:16 UTC, Insang Ryu
no flags Details
File: proc_pid_status (928 bytes, text/plain)
2013-01-25 09:17 UTC, Insang Ryu
no flags Details
File: var_log_messages (312 bytes, text/plain)
2013-01-25 09:17 UTC, Insang Ryu
no flags Details

Description Insang Ryu 2013-01-25 09:16:36 UTC
Description of problem:
I merged some commit in the terminal

Version-Release number of selected component:
gitg-0.2.5-4.fc18

Additional info:
backtrace_rating: 4
cmdline:        gitg
crash_function: slab_allocator_free_chunk
executable:     /usr/bin/gitg
kernel:         3.7.2-204.fc18.x86_64
remote_result:  846484
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 slab_allocator_free_chunk at gslice.c:1336
 #1 magazine_cache_trim at gslice.c:672
 #2 magazine_cache_push_magazine at gslice.c:703
 #3 thread_memory_magazine2_unload at gslice.c:802
 #4 g_slice_free1 at gslice.c:1093
 #5 g_type_free_instance at gtype.c:1935
 #6 gtk_container_destroy at gtkcontainer.c:1377
 #11 gtk_widget_dispose at gtkwidget.c:10270
 #13 gtk_widget_destroy at gtkwidget.c:3976
 #14 row_deleted_cb at gtktreemenu.c:941

Potential duplicate: bug 737245

Comment 1 Insang Ryu 2013-01-25 09:16:39 UTC
Created attachment 687335 [details]
File: backtrace

Comment 2 Insang Ryu 2013-01-25 09:16:41 UTC
Created attachment 687336 [details]
File: cgroup

Comment 3 Insang Ryu 2013-01-25 09:16:43 UTC
Created attachment 687337 [details]
File: core_backtrace

Comment 4 Insang Ryu 2013-01-25 09:16:47 UTC
Created attachment 687338 [details]
File: dso_list

Comment 5 Insang Ryu 2013-01-25 09:16:49 UTC
Created attachment 687339 [details]
File: environ

Comment 6 Insang Ryu 2013-01-25 09:16:51 UTC
Created attachment 687340 [details]
File: limits

Comment 7 Insang Ryu 2013-01-25 09:16:54 UTC
Created attachment 687341 [details]
File: maps

Comment 8 Insang Ryu 2013-01-25 09:16:56 UTC
Created attachment 687342 [details]
File: open_fds

Comment 9 Insang Ryu 2013-01-25 09:17:16 UTC
Created attachment 687343 [details]
File: proc_pid_status

Comment 10 Insang Ryu 2013-01-25 09:17:18 UTC
Created attachment 687344 [details]
File: var_log_messages

Comment 11 Scott Schmit 2013-02-03 16:00:12 UTC
I had gitg open to a git repository. I then, outside of gitg, modified the branch structure (I've done this several times, and I'm not sure which instance this crash corresponds to), renamed branches, deleted branches, done a git reset --hard HEAD~1, etc. Then I did a Control-R in gitg. Then it crashed.

backtrace_rating: 4
Package: gitg-0.2.5-4.fc18
OS Release: Fedora release 18 (Spherical Cow)

Comment 12 Fedora End Of Life 2013-12-21 10:49:07 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 13 Fedora End Of Life 2014-02-05 18:28:50 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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