Bug 801693
| Summary: | [abrt] evolution-3.2.3-1.fc16: _int_free: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dagan McGregor <bugzilla.redhat> | ||||||||||||
| Component: | evolution | Assignee: | Matthew Barnes <mbarnes> | ||||||||||||
| Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 16 | CC: | lucilanga, mbarnes, mcrha | ||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | x86_64 | ||||||||||||||
| OS: | Unspecified | ||||||||||||||
| Whiteboard: | abrt_hash:8600c9b6b62f5ddca6c11e48a8436750c2e5faf1 | ||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2012-03-12 10:24:52 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
Dagan McGregor
2012-03-09 07:26:06 UTC
Created attachment 568832 [details]
File: gconf_subtree
Created attachment 568833 [details]
File: build_ids
Created attachment 568834 [details]
File: dso_list
Created attachment 568835 [details]
File: maps
Created attachment 568836 [details]
File: backtrace
Thanks for a bug report. I checked the backtrace, but I do not see much from the crashing thread, it seems it crashed on thread finalization: Thread 1 (Thread 0x7fd81e1ed700 (LWP 2023)): #0 _int_free (av=0x7fd7e8000020, p=0x7fd7e8001440, have_lock=0) at malloc.c:4066 #1 0x0000003b8895d7ec in __res_iclose (statp=0x7fd81e1eddb8, free_addr=<optimized out>) at res_init.c:619 #2 res_thread_freeres () at res_init.c:646 #3 res_thread_freeres () at res_init.c:640 #4 0x0000003b8895d732 in __libc_thread_freeres () at thread-freeres.c:30 #5 0x0000003b88c07da3 in start_thread (arg=0x7fd81e1ed700) at pthread_create.c:319 #6 0x0000003b888f0f5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 which suggests that this is some kind of memory corruption. The other thing I can see from the backtrace is that there are quite many running imapx_parser_thread-s and imapx_idle_thread-s, which is rather unusual. One of the threads is also reconnecting to your mail server. I cannot tell much from any of these. Was there any kind of broken connection to the internet, or you server got offline unexpectedly, thus the imapx mail account was forced to reconnect? Maybe it's related to the issue. Also, did this happen only once, or you are able to reproduce this with certain steps? I'm asking, because memory corruption can be sometimes caught by valgrind. I believe you are right, I think this crash did happen about the same time as my wireless stopped working (ath9k known bug), and I believe Evolution was in the process of checking or loading email when it crashed. I haven't had this happen a second time yet, but thought it was worth reporting anyway, as I have had Evolution freak out a number of times, and it would be good if it handled these scenarios without crashing. I have 3 imapx accounts configured, all of them have mail sitting in them, one that holds my archive has a few thousand emails. The accounts all work normally, in this instance though I think it was a combination of a high number of emails and the wireless being killed. Thanks for the update. I think we can close this in favour of an upstream bug [1], which is about issues when unexpected disconnect & connect happens. There is also a bug #706413 from evolution 3.0.1, which describes just this, also with imapx being involved. [1] https://bugzilla.gnome.org/show_bug.cgi?id=650685 |