Version-Release number of selected component: evolution-data-server-3.6.2-3.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/libexec/evolution-addressbook-factory crash_function: bookview_stop_thread executable: /usr/libexec/evolution-addressbook-factory kernel: 3.7.2-204.fc18.x86_64 remote_result: NOTFOUND uid: 16777216 var_log_messages: Jan 23 12:53:59 polonkaigpc abrt[25268]: Saved core dump of pid 2256 (/usr/libexec/evolution-addressbook-factory) to /var/spool/abrt/ccpp-2013-01-23-12:53:56-2256 (314224640 bytes) Truncated backtrace: Thread no. 1 (2 frames) #6 bookview_stop_thread at e-data-book-view.c:681 #7 g_thread_proxy at gthread.c:797
Created attachment 685878 [details] File: backtrace
Created attachment 685879 [details] File: cgroup
Created attachment 685880 [details] File: core_backtrace
Created attachment 685881 [details] File: dso_list
Created attachment 685882 [details] File: environ
Created attachment 685883 [details] File: limits
Created attachment 685884 [details] File: maps
Created attachment 685885 [details] File: open_fds
Created attachment 685886 [details] File: proc_pid_status
Created attachment 685887 [details] File: smolt_data
Thanks for a bug report. The backtrace suggests that the crash happened due to "double free or corruption" during a g_free() call, though the line where it points doesn't have there any such call, thus it might be related to some of your address book you've configured. Could you write here a list of address books you've configured, please? it's like On This Computer/LDAP/..., I'm not interested in the server where they connect, I'm interested only in the addressbook types. Thanks in advance. Also, are you able to reproduce this after certain steps, or was it just an occasional crash, please?
It was just an occasional crash. At the time I had three Google accounts from GOA, and the company's Active Directory set up as an LDAP backend. Also, the address autocomplete feature made evolution hanging for a while (about a minute or so), then completion failed, so I had to type the whole address anyway. I don't know, if it's related, but since I removed the LDAP address book, everything work smoothly.
Thanks for the update. It sounds like you faced [1] too. I do not see anything obvious in LDAP's book_view_stop() handler, there is a g_free() call, but whether it can actually happen that the book_view_stop() is called multiple times on one object I do not know, I would guess it's not, but your above backtrace suggests something else. [1] https://bugzilla.gnome.org/show_bug.cgi?id=692278
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.
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.