Red Hat Bugzilla – Bug 984891
[abrt] gitg-0.2.7-1.fc19: mem_error: Process /usr/bin/gitg was killed by signal 6 (SIGABRT)
Last modified: 2015-02-17 11:11:09 EST
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#2 mem_error at gslice.c:1442
#3 slab_allocator_free_chunk at gslice.c:1324
#4 magazine_cache_trim at gslice.c:672
#5 magazine_cache_push_magazine at gslice.c:703
#6 thread_memory_magazine2_unload at gslice.c:802
#7 g_slice_free1 at gslice.c:1093
#8 do_clear at gitg-repository.c:385
#9 gitg_repository_reload at gitg-repository.c:1520
#14 _gtk_action_emit_activate at gtkaction.c:801
#19 gtk_widget_activate at gtkwidget.c:6745
Potential duplicate: bug 706381
Created attachment 774148 [details]
Created attachment 774149 [details]
Created attachment 774150 [details]
Created attachment 774151 [details]
Created attachment 774152 [details]
Created attachment 774153 [details]
Created attachment 774154 [details]
Created attachment 774155 [details]
Created attachment 774156 [details]
Created attachment 774157 [details]
I had gitg on another workspace when it crashed but the repo I had open I was working on via command line. I had merged a feature branch with the develop branch, pushed to origin, then merged develop with master and pushed to origin. I then created a lightweight tag " git tag v1.2.1 " and pushed to origin. All via command line. I am not sure which one of these operations killed gitg.
reason: Process /usr/bin/gitg was killed by signal 6 (SIGABRT)
runlevel: N 5
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 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 this bug is closed as described in the policy above.
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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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
Thank you for reporting this bug and we are sorry it could not be fixed.