Version-Release number of selected component: evolution-data-server-3.6.4-3.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/libexec/evolution-calendar-factory crash_function: g_thread_new executable: /usr/libexec/evolution-calendar-factory kernel: 3.8.8-202.fc18.x86_64 uid: 1000 ureports_counter: 1 xsession_errors: Truncated backtrace: Thread no. 1 (10 frames) #2 g_thread_new at gthread.c:838 #3 impl_DataCalView_start at e-data-cal-view.c:475 #4 e_gdbus_marshallers_BOOLEAN__OBJECT at e-gdbus-marshallers.c:124 #9 e_gdbus_stub_handle_method_call at e-gdbus-templates.c:679 #10 call_in_idle_cb at gdbusconnection.c:4737 #15 dbus_server_run_server at e-dbus-server.c:222 #16 ffi_call_unix64 at ../src/x86/unix64.S:75 #17 ffi_call at ../src/x86/ffi64.c:486 #18 g_cclosure_marshal_generic_va at gclosure.c:1550 #19 _g_closure_invoke_va at gclosure.c:840
Created attachment 748979 [details] File: backtrace
Created attachment 748980 [details] File: cgroup
Created attachment 748981 [details] File: core_backtrace
Created attachment 748982 [details] File: dso_list
Created attachment 748983 [details] File: environ
Created attachment 748984 [details] File: limits
Created attachment 748985 [details] File: maps
Thanks for a bug report. A similar upstream report is [1], against pitivi, where user found a workaround to not set stack limit. Do you have that set intentionally? Or maybe you just had evolution-data-server running too long, and it leaked too much of memory? I see in comment #6 attachment that you have set a stack size limit. [1] https://bugzilla.gnome.org/show_bug.cgi?id=662295
*** Bug 969842 has been marked as a duplicate of this bug. ***
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.