Description of problem: I simply clicked on a new email message to read it. Evolution had been open for 15 minutes prior to this crash. Version-Release number of selected component: evolution-3.6.4-2.fc18 Additional info: backtrace_rating: 4 cmdline: evolution crash_function: g_try_malloc executable: /usr/bin/evolution kernel: 3.8.4-202.fc18.x86_64 uid: 25561 var_log_messages: Mar 26 10:47:56 euler abrt[14623]: Saved core dump of pid 11960 (/usr/bin/evolution) to /var/spool/abrt/ccpp-2013-03-26-10:47:54-11960 (1299218432 bytes) Truncated backtrace: Thread no. 1 (8 frames) #3 g_try_malloc at gmem.c:310 #4 gdk_pixbuf_save_to_bufferv at gdk-pixbuf-io.c:2700 #5 gdk_pixbuf_save_to_buffer at gdk-pixbuf-io.c:2623 #6 get_empty_image_stream at e-mail-request.c:208 #7 handle_contact_photo_request at e-mail-request.c:264 #8 run_in_thread at gsimpleasyncresult.c:869 #9 io_job_thread at gioscheduler.c:162 #11 g_thread_proxy at gthread.c:797
Created attachment 716562 [details] File: backtrace
Created attachment 716563 [details] File: cgroup
Created attachment 716564 [details] File: core_backtrace
Created attachment 716565 [details] File: dso_list
Created attachment 716566 [details] File: environ
Created attachment 716567 [details] File: limits
Created attachment 716568 [details] File: maps
Created attachment 716569 [details] File: open_fds
Created attachment 716570 [details] File: proc_pid_status
Created attachment 716571 [details] File: smolt_data
Thanks for a bug report. The backtrace shows that this crashed during memory allocation of 1024 bytes. I cannot tell for sure, but it seems to me that the cause was a memory corruption, which could be caused by anything during those 15 minutes of run. Did this happen to you just once, or you can reproduce this reliably? I do not recall seeing any such crash myself, neither I can find anything similar in the upstream bugzilla (with 'handle_contact_photo_request').
(In reply to comment #11) > Thanks for a bug report. The backtrace shows that this crashed during memory > allocation of 1024 bytes. I cannot tell for sure, but it seems to me that > the cause was a memory corruption, which could be caused by anything during > those 15 minutes of run. Did this happen to you just once, or you can > reproduce this reliably? I do not recall seeing any such crash myself, > neither I can find anything similar in the upstream bugzilla (with > 'handle_contact_photo_request'). This was pretty much an isolated event - it happened 3 times since the upgrade to F18. The much more common event is that evolution simply locks up (the status bar generates many "saving user interface" and "retrieving message" indications). At this point the only way to terminate evolution is with a kill -9. Since I have to do that 4 or 5 times a day, I wrote a script to handle killing off evolution. I am not sure if these is related. But this also started immediately after the upgrade (via fedup) to F18. Evolution worked without an issue prior to the upgrade. Please let me know if there is anything else I can provide.
Hrm, evolution 3.6.x tends to lockup on contact photo lookups. As a workaround, you can try to disable an option in Edit->Preferences->Mail Preferences, tab Headers, Show sender's photograph.... Similar in HTML Messages tab, do not "Load images is sender in my addressbook". With respect of this particular crash, I'm not sure how to follow on it. If it's just an occasional crash, then it might mean that a reproducer is complicated, depending on various data or current evolution state, when proper timing triggers the crash (and/or memory corruption).
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.