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 637836 - camel memory corruption / crash ...
camel memory corruption / crash ...
Status: RESOLVED DUPLICATE of bug 637305
Product: evolution
Classification: Applications
Component: Mailer
2.32.x (obsolete)
Other Linux
: Normal blocker
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-12-22 22:03 UTC by Michael Meeks
Modified: 2011-02-11 12:07 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
complete valgrind log to the crash. (16.64 KB, text/plain)
2010-12-22 22:05 UTC, Michael Meeks
Details

Description Michael Meeks 2010-12-22 22:03:59 UTC
Currently I can't use evo for more than about 30 minutes without getting this crash, or a (perhaps related) lock-up in some sql foo, but anyhow - despairing of mail reading, I ran it under valgrind; I append the complete log; some interesting things like this:

==753== Thread 15:
==753== Invalid read of size 4
==753==    at 0x4C3A040: camel_partition_table_lookup (camel-partition-table.c:299)
==753==    by 0x4C423DA: hash_write_word (camel-text-index.c:250)
==753==    by 0x469E112: g_hash_table_foreach (ghash.c:1328)
==753==    by 0x4C4210A: text_index_write_name (camel-text-index.c:724)
==753==    by 0x4C17839: camel_index_write_name (camel-index.c:240)
==753==    by 0x534269B: camel_folder_summary_info_new_from_message (camel-folder-summary.c:2754)
==753==    by 0x5342B15: camel_folder_summary_add_from_message (camel-folder-summary.c:2606)
==753==    by 0xFB34715: local_summary_add (camel-local-summary.c:496)
==753==    by 0xFB392ED: mbox_summary_add (camel-mbox-summary.c:1282)
==753==    by 0xFB34B71: camel_local_summary_add (camel-local-summary.c:327)
==753==    by 0xFB35CFF: mbox_append_message (camel-mbox-folder.c:180)
==753==    by 0x534AF82: camel_folder_append_message (camel-folder.c:1415)
==753==  Address 0x74ff464 is 4 bytes after a block of size 1,048 alloc'd
==753==    at 0x40274A5: calloc (vg_replace_malloc.c:467)
==753==    by 0x46B6379: g_malloc0 (gmem.c:196)
==753==    by 0x4C092CB: camel_block_file_get_block (camel-block-file.c:573)
==753==    by 0x4C3A019: camel_partition_table_lookup (camel-partition-table.c:288)
==753==    by 0x4C423DA: hash_write_word (camel-text-index.c:250)
==753==    by 0x469E112: g_hash_table_foreach (ghash.c:1328)
==753==    by 0x4C4210A: text_index_write_name (camel-text-index.c:724)
==753==    by 0x4C17839: camel_index_write_name (camel-index.c:240)
==753==    by 0x534269B: camel_folder_summary_info_new_from_message (camel-folder-summary.c:2754)
==753==    by 0x5342B15: camel_folder_summary_add_from_message (camel-folder-summary.c:2606)
==753==    by 0xFB34715: local_summary_add (camel-local-summary.c:496)
==753==    by 0xFB392ED: mbox_summary_add (camel-mbox-summary.c:1282)
==753== 

are concerning.
Comment 1 Michael Meeks 2010-12-22 22:05:12 UTC
Created attachment 176902 [details]
complete valgrind log to the crash.

I'm using:

evolution-data-server-2.32.20101220-1.1.i586
evolution-2.32.20101220-1.1.i586
Comment 2 Akhil Laddha 2010-12-23 05:17:09 UTC
duplicate of bug 637305 ?
Comment 3 Milan Crha 2011-02-11 12:07:46 UTC
(In reply to comment #2)
> duplicate of bug 637305 ?

I suppose it's at least related, thus I'm marking it as a duplicate.

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