Description of problem: I added some files for a commit, wrote the commit message and clicked on "commit". Then the program crashed. I checked with git status and the commit seemed to be successful Version-Release number of selected component: gitg-0.2.5-3.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: gitg crash_function: slab_allocator_free_chunk kernel: 3.7.3-101.fc17.x86_64 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_nodes_free at gnode.c:124 : #6 g_node_destroy at gnode.c:144 : #7 gtk_tree_store_remove at gtktreestore.c:1230 : #8 clear_branches_combo at gitg-window.c:1422 : #9 on_repository_load at gitg-window.c:1707 Potential duplicate bug: 737245
Created attachment 691608 [details] File: core_backtrace
Created attachment 691609 [details] File: environ
Created attachment 691610 [details] File: limits
Created attachment 691611 [details] File: backtrace
Created attachment 691612 [details] File: cgroup
Created attachment 691613 [details] File: smolt_data
Created attachment 691614 [details] File: executable
Created attachment 691615 [details] File: maps
Created attachment 691616 [details] File: dso_list
Created attachment 691617 [details] File: proc_pid_status
Created attachment 691618 [details] File: var_log_messages
Created attachment 691619 [details] File: open_fds
I was browsing the history tree when the application crashed. backtrace_rating: 4 cmdline: gitg crash_function: slab_allocator_free_chunk executable: /usr/bin/gitg kernel: 3.8.4-102.fc17.x86_64 package: gitg-0.2.5-3.fc17 reason: Process /usr/bin/gitg was killed by signal 11 (SIGSEGV) uid: 1000 ureports_counter: 1 xsession_errors: (gnome-settings-daemon:17848): updates-plugin-WARNING **: failed to refresh the cache: Yum is locked by another application. The other process has the command line '/usr/bin/python /bin/yum install gitg gitk' (PID 17687)
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 17'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.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.