Bug 508460
Summary: | Evolution segfault using maildir format | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jens Falsmar Oechsler <joe> | ||||
Component: | evolution | Assignee: | Matthew Barnes <mbarnes> | ||||
Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 11 | CC: | mbarnes, mcrha | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2009-06-28 15:04:54 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Jens Falsmar Oechsler
2009-06-27 12:11:09 UTC
Moving this upstream for better visibility. Please see [1] for further updates. [1] http://bugzilla.gnome.org/show_bug.cgi?id=587206 Anything I can test or do to help solve this in Fedora? Or ask upstream? Lots of duplicates filed on the gnome bug report but no comments. Hi Jens, if you can reproduce reliably, then it would be great to help. The best might be some steps and/or data to reproduce it, as it would help much with the debugging and finding proper fix, though I'm not sure whether this is possible here. With a bit of luck we may try valgrind, whether it'll show us what's happening with a memory. Could you try this, please: a) close evolution b) on console run: $ valgrind --leak-check=full evolution &>v.log c) when it crashes or something, and valgrind will stop, attach here the v.log file, it might contain some information we are looking for. Just note that running evolution under valgrind is significantly slower. Created attachment 354581 [details]
valgrind --leak-check=full
When running Evolution under Valgrind I didn't see any crashes. Still happens when running Evolution normally.
Thanks for the update, I see nothing unusual in the valgrind output you uploaded here, maybe only except of the below. The reason for not crashing under valgrind I believe is the slowness, it doesn't have time to overlap in the "correct order".
> (evolution:6906): camel-CRITICAL **: camel_message_info_free: assertion
> `mi != NULL' failed
> Thread 10:
> Invalid write of size 8
> at 0xE30C608: (within /usr/lib64/gtk-2.0/modules/libgnomebreakpad.so)
> by 0x3528641A18: g_logv (in /lib64/libglib-2.0.so.0.2000.4)
> by 0x3528641DB2: g_log (in /lib64/libglib-2.0.so.0.2000.4)
> by 0x13D5BA3D: maildir_summary_sync (camel-maildir-summary.c:809)
> by 0x13D4FAF6: local_sync (camel-local-folder.c:517)
> by 0x63F4FB0: camel_folder_sync (camel-folder.c:324)
> by 0xF73EC6C: refresh_folders_exec (mail-send-recv.c:828)
> by 0xF7390EE: mail_msg_proxy (mail-mt.c:520)
> by 0x3528661F31: (within /lib64/libglib-2.0.so.0.2000.4)
> by 0x3528660933: (within /lib64/libglib-2.0.so.0.2000.4)
> by 0x35B2606869: start_thread (in /lib64/libpthread-2.10.1.so)
> by 0x35B1ADE25C: clone (in /lib64/libc-2.10.1.so)
> Address 0x1b7147c8 is 0 bytes after a block of size 128 alloc'd
> at 0x4A05414: calloc (vg_replace_malloc.c:397)
> by 0x3528640297: g_malloc0 (in /lib64/libglib-2.0.so.0.2000.4)
> by 0xE30C5F9: (within /usr/lib64/gtk-2.0/modules/libgnomebreakpad.so)
> by 0x3528641A18: g_logv (in /lib64/libglib-2.0.so.0.2000.4)
> by 0x3528641DB2: g_log (in /lib64/libglib-2.0.so.0.2000.4)
> by 0x13D5BA3D: maildir_summary_sync (camel-maildir-summary.c:809)
> by 0x13D4FAF6: local_sync (camel-local-folder.c:517)
> by 0x63F4FB0: camel_folder_sync (camel-folder.c:324)
> by 0xF73EC6C: refresh_folders_exec (mail-send-recv.c:828)
> by 0xF7390EE: mail_msg_proxy (mail-mt.c:520)
> by 0x3528661F31: (within /lib64/libglib-2.0.so.0.2000.4)
> by 0x3528660933: (within /lib64/libglib-2.0.so.0.2000.4)
|