Version-Release number of selected component: gitg-0.2.5-4.fc18 Additional info: backtrace_rating: 4 cmdline: gitg crash_function: mem_error executable: /usr/bin/gitg kernel: 3.7.1-2.fc18.x86_64 remote_result: 795135 uid: 1000 var_log_messages: Jan 9 15:07:10 localhost abrt[10485]: Saved core dump of pid 10426 (/usr/bin/gitg) to /var/spool/abrt/ccpp-2013-01-09-15:07:08-10426 (63414272 bytes) Truncated backtrace: 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 real_node_free at gsequence.c:1806 #9 node_free at gsequence.c:1816 #10 g_sequence_remove at gsequence.c:542 #11 gtk_list_store_remove at gtkliststore.c:1228 Potential duplicate: bug 706381
Created attachment 675634 [details] File: backtrace
Created attachment 675635 [details] File: cgroup
Created attachment 675636 [details] File: core_backtrace
Created attachment 675637 [details] File: dso_list
Created attachment 675638 [details] File: environ
Created attachment 675639 [details] File: limits
Created attachment 675640 [details] File: maps
Created attachment 675641 [details] File: open_fds
Created attachment 675642 [details] File: proc_pid_status
I was cherry-picking from one branch to another, and this seemed to happen randomly. I don't know if it's reproduceable, it seemed like it might be spontaneous. It might be worth mentioning that the 2 branches I was dealing with were completely different, no common parent commits among them. backtrace_rating: 4 Package: gitg-0.2.5-4.fc18 OS Release: Fedora release 18 (Spherical Cow)
I was renaming branches, doing reset --hard HEAD~1, etc (I had multiple crashes, I'm not sure which this goes with) outside of gitg. Then I hit Control-R in gitg and it crashed. backtrace_rating: 4 Package: gitg-0.2.5-4.fc18 OS Release: Fedora release 18 (Spherical Cow)
Running gitg in a working directory and changing branch several times from command line. backtrace_rating: 4 Package: gitg-0.2.5-4.fc18 OS Release: Fedora release 18 (Spherical Cow)
Cyclically switch branches in my small git and after several switches gitg suddenly crashes. reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: gitg crash_function: mem_error executable: /usr/bin/gitg kernel: 3.9.9-201.fc18.x86_64 package: gitg-0.2.5-4.fc18 reason: Process /usr/bin/gitg was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 1000 xsession_errors: ***MEMORY-ERROR***: gitg[3650]: GSlice: assertion failed: sinfo->n_allocated > 0
I delete one branch from command line and gitg, which was opened for browsing this git repo on another branch crashes. reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: gitg crash_function: mem_error executable: /usr/bin/gitg kernel: 3.9.9-201.fc18.x86_64 package: gitg-0.2.5-4.fc18 reason: Process /usr/bin/gitg was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 1000
This is a common problem, but not 100% reproducible. In this case I had just created/changed branches & then refreshed the display while it showed all branches. Then it crashed. Re-opening gitg in the same repository/branch/etc did not cause gitg to crash again. reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: gitg crash_function: mem_error executable: /usr/bin/gitg kernel: 3.9.6-200.fc18.x86_64 package: gitg-0.2.5-4.fc18 reason: Process /usr/bin/gitg was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 1000 xsession_errors:
Ran git fetch while gitg was displaying all branches. reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: gitg . --all crash_function: mem_error executable: /usr/bin/gitg kernel: 3.10.10-100.fc18.x86_64 package: gitg-0.2.5-4.fc18 reason: Process /usr/bin/gitg was killed by signal 6 (SIGABRT) runlevel: N 3 type: CCpp uid: 15550
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.
At the very minimum, this problem still exists in Fedora 19.
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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.