Bug 637305 – crash reading mail

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 637305 - crash reading mail


Summary:	crash reading mail


Status:	RESOLVED DUPLICATE of bug 632312

Product:	evolution
Classification:	Applications
Component:	Mailer
Version:	2.32.x (obsolete)
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	evolution-mail-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Duplicates:	637836 644431 644735 (view as bug list)
Depends on:
Blocks:

Reported:	2010-12-15 14:14 UTC by Michael Meeks
Modified:	2011-03-15 01:21 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Michael Meeks 2010-12-15 14:14:57 UTC

I have: evolution-2.32.20101208-1.3.i586 and a matching e-d-s from the same day.

(evolution:25493): camel-local-provider-WARNING **: The next message didn't start where I expected, building summary from start
[Thread 0xa04ffb70 (LWP 28174) exited]
[New Thread 0xa04ffb70 (LWP 28175)]
[Thread 0xa04ffb70 (LWP 28175) exited]
*** buffer overflow detected ***: /usr/bin/evolution terminated
======= Backtrace: =========
Program received signal SIGABRT, Aborted.

+ Trace 225141

Thread 2875194224 (LWP 28118)

#0 __kernel_vsyscall
#1 raise
from /lib/libc.so.6
#2 abort
from /lib/libc.so.6
#3 __libc_message
from /lib/libc.so.6
#4 __fortify_fail
from /lib/libc.so.6
#5 __chk_fail
from /lib/libc.so.6
#6 memcpy
at /usr/include/bits/string3.h line 52
#7 camel_partition_table_add
at camel-partition-table.c line 556
#8 text_index_add_name
at camel-text-index.c line 689
#9 camel_index_add_name
at camel-index.c line 224
#10 camel_folder_summary_info_new_from_parser
at camel-folder-summary.c line 2687
#11 camel_folder_summary_add_from_parser
at camel-folder-summary.c line 2587
#12 summary_update
at camel-mbox-summary.c line 520
#13 mbox_summary_check
at camel-mbox-summary.c line 645
#14 camel_local_summary_check
at camel-local-summary.c line 277
#15 mbox_summary_sync
at camel-mbox-summary.c line 976
#16 camel_local_summary_sync
at camel-local-summary.c line 313
#17 local_sync
at camel-local-folder.c line 524
#18 camel_folder_sync
at camel-folder.c line 1124
#19 send_queue_exec
at mail-ops.c line 845
#20 mail_msg_proxy
at mail-mt.c line 469
#21 g_thread_pool_thread_proxy
at gthreadpool.c line 319
#22 g_thread_create_proxy
at gthread.c line 1897
#23 start_thread
at pthread_create.c line 297
#24 clone
from /lib/libc.so.6


All other threads quiescent.

Comment 1 Michael Meeks 2010-12-15 14:17:05 UTC

(gdb)

+ Trace 225142

#7 camel_partition_table_add
at camel-partition-table.c line 556
#8 text_index_add_name
at camel-text-index.c line 689
#9 camel_index_add_name
at camel-index.c line 224

$6 = {parent_class = {parent_class = {g_type_class = {g_type = 139571360}, construct_properties = 0x82172c8 = {0x80c7e50}, constructor = 0xb79b71c0 <g_object_constructor>, set_property = 
    0, get_property = 0, dispose = 0xb73e29b0 <text_index_dispose>, finalize = 0xb73e28c0 <text_index_finalize>, dispatch_properties_changed = 
    0xb79b6890 <g_object_dispatch_properties_changed>, notify = 0, constructed = 0, flags = 1, pdummy = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0}}, state_read = 0xb73d6800 <object_state_read>, 
    state_write = 0xb73d6600 <object_state_write>}, sync = 0xb73e3640 <text_index_sync>, compress = 0xb73e35d0 <text_index_compress>, delete = 0xb73e2840 <text_index_delete>, rename = 
    0xb73e26a0 <text_index_rename>, has_name = 0xb73e2650 <text_index_has_name>, add_name = 0xb73e4ba0 <text_index_add_name>, write_name = 0xb73e20a0 <text_index_write_name>, find_name = 
    0xb73e1d80 <text_index_find_name>, delete_name = 0xb73e21f0 <text_index_delete_name>, find = 0xb73e50b0 <text_index_find>, words = 0xb73e5550 <text_index_words>, names = 
    0xb73e5500 <text_index_names>}

in case it helps :-)

Comment 2 Akhil Laddha 2010-12-16 04:00:48 UTC

duplicate of bug 632312 ?

Comment 3 Michael Meeks 2010-12-16 13:58:02 UTC

Looks like it, but with a cleaner trace I guess - obviously some memory corruption, somewhere ;-)

Comment 4 Michael Meeks 2010-12-16 16:19:20 UTC

I just got another crash, perhaps the same thing:

(evolution:28213): camel-WARNING **: Block 4400: Invalid index or content: index 14 used 835748436


(evolution:28213): camel-WARNING **: Could not find key entry for word 'the': No such file or directory


Program received signal SIGSEGV, Segmentation fault.

+ Trace 225157

Thread 2530188144 (LWP 14758)

#0 camel_partition_table_lookup
at camel-partition-table.c line 299
#1 text_index_add_name_to_word
at camel-text-index.c line 250
#2 hash_write_word
at camel-text-index.c line 711
#3 g_hash_table_foreach
at ghash.c line 1328
#4 text_index_write_name
at camel-text-index.c line 724
#5 camel_index_write_name
at camel-index.c line 240
#1 text_index_add_name_to_word
at camel-text-index.c line 250
#0 camel_partition_table_lookup
at camel-partition-table.c line 299

Thread 19455 (Thread 0x96cf9b70 (LWP 14758))

#0 camel_partition_table_lookup
at camel-partition-table.c line 299
#1 text_index_add_name_to_word

Comment 5 Michael Meeks 2011-01-05 15:56:41 UTC

yes dup. I hit this every day, often a couple of times per day :-)

*** This bug has been marked as a duplicate of bug 632312 ***

Comment 6 Milan Crha 2011-02-11 12:07:46 UTC

*** Bug 637836 has been marked as a duplicate of this bug. ***

Comment 7 Akhil Laddha 2011-03-11 01:20:30 UTC

*** Bug 644431 has been marked as a duplicate of this bug. ***

Comment 8 Fabio Durán Verdugo 2011-03-15 01:21:16 UTC

*** Bug 644735 has been marked as a duplicate of this bug. ***