GNOME Bugzilla – Bug 619106
Crash in free_message_info_data at message-list.c line 4425
Last modified: 2011-02-03 09:45:04 UTC
What were you doing when the application crashed? grouped mails by threads Distribution: Debian squeeze/sid Gnome Release: 2.30.0 2010-04-26 (Debian) BugBuddy Version: 2.30.0 System: Linux 2.6.32-fermat #1 SMP PREEMPT Mon Apr 26 14:26:49 CEST 2010 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10707000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Tango GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 815919104 vsize: 815919104 resident: 130260992 share: 24387584 rss: 130260992 rss_rlim: 18446744073709551615 CPU usage: start_time: 1274286777 rtime: 1107 utime: 1020 stime: 87 cutime:61 cstime: 13 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0x7fd2ebb23910 (LWP 5905)] [New Thread 0x7fd2ef530910 (LWP 5893)] [New Thread 0x7fd2f5b19910 (LWP 5892)] [New Thread 0x7fd302ad0910 (LWP 5870)] [New Thread 0x7fd3032d1910 (LWP 5869)] 0x00007fd30d565633 in *__GI___poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=81) at ../sysdeps/unix/sysv/linux/poll.c:87 in ../sysdeps/unix/sysv/linux/poll.c
+ Trace 221990
Thread 2 (Thread 0x7fd2ebb23910 (LWP 5905))
A debugging session is active. Inferior 1 [process 5867] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors --------------------- 7fd316fe3000-7fd316fee000 r--s 00000000 08:01 6062129 /var/cache/fontconfig/e13b20fdb08344e0e664864cc2ede53d-le64.cache-3 7fd316fee000-7fd31701d000 rw-p 00000000 00:00 0 7fd31701d000-7fd317021000 r--s 00000000 08:01 6062381 /var/cache/fontconfig/0dad82dbaa6c15cf0806f139d62298a3-le64.cache-3 7fd317021000-7fd317023000 r--s 00000000 08:01 6062380 /var/cache/fontconfig/6fe0ed9ceabbaa79283ea9c0b49c5d6e-le64.cache-3 7fd317023000-7fd317025000 r--s 00000000 08:01 6062367 /var/cache/fontconfig/ae26c1aac6606cb24499bf89ff8f20df-le64.cache-3 7fd317025000-7fd317027000 r--s 00000000 08:01 6062378 /var/cache/fontconfig/5b0623c2c1e6dea9559ee397e26a7919-le64.cache-3 7fd317027000-7fd317029000 r--s 00000000 08:01 6062236 /var/cache/fontconfig/7ef2298fde41cc6eeb7af42e48b7d293-le64.cache-3 7fd317029000-7fd317035000 r--s 00000000 08:02 6031170 /home/calestyo/.fontconfig/ddcbdbd977b5ff50d9e36c8f351aad43-le64.cache-3 7fd317035000-7fd31703d000 rw-p 00000000 00:00 0 7fd31703d000-7fd31703e000 r--p 0001c000 08:01 9633818 /lib/ld-2.10.2.so 7fd31703e000-7fd31703f000 rw-p 0001d000 08:01 9633818 /lib/ld-2.10.2.so 7fff7b799000-7fff7b7b4000 rw-p 00000000 00:00 0 [stack] 7fff7b7ff000-7fff7b800000 r-xp 00000000 00:00 0 [vdso] ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall] 87 ../sysdeps/unix/sysv/linux/poll.c: No such file or directory. --------------------------------------------------
*** Bug 619132 has been marked as a duplicate of this bug. ***
*** Bug 619118 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
*** Bug 621673 has been marked as a duplicate of this bug. ***
*** Bug 621910 has been marked as a duplicate of this bug. ***
*** Bug 620692 has been marked as a duplicate of this bug. ***
*** Bug 622097 has been marked as a duplicate of this bug. ***
*** Bug 622851 has been marked as a duplicate of this bug. ***
*** Bug 622949 has been marked as a duplicate of this bug. ***
*** Bug 622983 has been marked as a duplicate of this bug. ***
*** Bug 623329 has been marked as a duplicate of this bug. ***
*** Bug 623368 has been marked as a duplicate of this bug. ***
*** Bug 623410 has been marked as a duplicate of this bug. ***
*** Bug 623465 has been marked as a duplicate of this bug. ***
*** Bug 623483 has been marked as a duplicate of this bug. ***
*** Bug 623522 has been marked as a duplicate of this bug. ***
*** Bug 623602 has been marked as a duplicate of this bug. ***
*** Bug 623716 has been marked as a duplicate of this bug. ***
*** Bug 623894 has been marked as a duplicate of this bug. ***
*** Bug 625049 has been marked as a duplicate of this bug. ***
*** Bug 625412 has been marked as a duplicate of this bug. ***
*** Bug 625951 has been marked as a duplicate of this bug. ***
PLEASE AVOID REPORTING THE SAME PROBLEM ALL OVER AGAIN and instead read https://bugzilla.gnome.org/show_bug.cgi?id=619106#c3 . Thanks.
*** Bug 626816 has been marked as a duplicate of this bug. ***
*** Bug 626817 has been marked as a duplicate of this bug. ***
*** Bug 626818 has been marked as a duplicate of this bug. ***
*** Bug 626820 has been marked as a duplicate of this bug. ***
*** Bug 626825 has been marked as a duplicate of this bug. ***
*** Bug 626835 has been marked as a duplicate of this bug. ***
Nice trace in bug 626842
+ Trace 223227
*** Bug 626842 has been marked as a duplicate of this bug. ***
(In reply to comment #3) > Thanks for taking the time to report this bug. > Unfortunately, that stack trace is missing some elements that will help a lot > to solve the problem, so it will be hard for the developers to fix that crash. > Can you get us a stack trace with debugging symbols? Please see > http://live.gnome.org/GettingTraces for more information on how to do so and > reopen this bug or report a new one. Thanks in advance! Someone reported (it seems) the same bug in Debian BTS at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598123 There's a backtrace: (gdb) bt full
+ Trace 223901
Thread 1 (Thread 0x7ffff7fb9800 (LWP 16475))
Thanks for a bug report. What are console message from time of the crash, please? I suppose there are some runtime critical warnings printed. Also, can you reproduce this anyhow, please? (I'm also grouping messages by threads.) I noticed something similar, I've on console shown: > evolution-mail-CRITICAL **: cmp_array_uids: assertion `md1->mi != NULL' > failed > camel-CRITICAL **: camel_folder_free_message_info: assertion `info != NULL' > failed when changing between search folders, but it never crashes for me, thus it can be unrelated to your issue.
Hi, I'm the reporter of Debian bug #598123. I do not have such errors. All I got is that: $ evolution Xlib: extension "RANDR" missing on display "localhost:10.0". *** glibc detected *** evolution: munmap_chunk(): invalid pointer: 0x00007f55af2616a0 *** ======= Backtrace: ========= /lib/libc.so.6(+0x71ad6)[0x7f55b5a70ad6] /usr/lib/evolution/2.30/libevolution-mail.so.0(+0x8b486)[0x7f55af24e486] /lib/libglib-2.0.so.0(g_hash_table_foreach+0x43)[0x7f55b5d8fc13] /usr/lib/evolution/2.30/libevolution-mail.so.0(+0x8c456)[0x7f55af24f456] /usr/lib/evolution/2.30/libevolution-mail.so.0(+0x7d3c8)[0x7f55af2403c8] /lib/libglib-2.0.so.0(+0x695cf)[0x7f55b5dc95cf] /lib/libglib-2.0.so.0(+0x67784)[0x7f55b5dc7784] /lib/libpthread.so.0(+0x68ba)[0x7f55b9aca8ba] /lib/libc.so.6(clone+0x6d)[0x7f55b5ace02d] ======= Memory map: ======== 00400000-00404000 r-xp 00000000 fe:00 147523 /usr/bin/evolution 00604000-00605000 rw-p 00004000 fe:00 147523 /usr/bin/evolution 02140000-038ca000 rw-p 00000000 00:00 0 [heap] 7f5597294000-7f5597296000 r-xp 00000000 fe:00 165290 /usr/lib/gconv/ISO8859-1.so 7f5597296000-7f5597495000 ---p 00002000 fe:00 165290 /usr/lib/gconv/ISO8859-1.so 7f5597495000-7f5597496000 r--p 00001000 fe:00 165290 /usr/lib/gconv/ISO8859-1.so 7f5597496000-7f5597497000 rw-p 00002000 fe:00 165290 /usr/lib/gconv/ISO8859-1.so 7f5597497000-7f5597498000 ---p 00000000 00:00 0 7f5597498000-7f5597c98000 rw-p 00000000 00:00 0 7f5597c98000-7f5597c99000 ---p 00000000 00:00 0 7f5597c99000-7f5598499000 rw-p 00000000 00:00 0 7f5598499000-7f559849d000 r-xp 00000000 fe:00 304994 /usr/lib/evolution/2.30/plugins/liborg-gnome-face.so 7f559849d000-7f559869c000 ---p 00004000 fe:00 304994 /usr/lib/evolution/2.30/plugins/liborg-gnome-face.so 7f559869c000-7f559869d000 rw-p 00003000 fe:00 304994 /usr/lib/evolution/2.30/plugins/liborg-gnome-face.so 7f559869d000-7f55986ec000 r--p 00000000 fe:00 262044 /usr/share/fonts/truetype/ttf-dejavu/DejaVuSansMono.ttf 7f559993a000-7f55999c9000 r--p 00000000 fe:00 262045 /usr/share/fonts/truetype/ttf-dejavu/DejaVuSans-Bold.ttf 7f55999c9000-7f55999cd000 r-xp 00000000 fe:00 304991 /usr/lib/evolution/2.30/plugins/liborg-gnome-backup-restore.so 7f55999cd000-7f5599bcc000 ---p 00004000 fe:00 304991 /usr/lib/evolution/2.30/plugins/liborg-gnome-backup-restore.so 7f5599bcc000-7f5599bcd000 rw-p 00003000 fe:00 304991 /usr/lib/evolution/2.30/plugins/liborg-gnome-backup-restore.so 7f5599bcd000-7f5599bd3000 r-xp 00000000 fe:00 305001 /usr/lib/evolution/2.30/plugins/liborg-gnome-templates.so 7f5599bd3000-7f5599dd3000 ---p 00006000 fe:00 305001 /usr/lib/evolution/2.30/plugins/liborg-gnome-templates.so 7f5599dd3000-7f5599dd4000 rw-p 00006000 fe:00 305001 /usr/lib/evolution/2.30/plugins/liborg-gnome-templates.so 7f5599dd4000-7f5599dd8000 r-xp 00000000 fe:00 272827 /usr/lib/evolution/2.30/plugins/liborg-gnome-plugin-manager.so 7f5599dd8000-7f5599fd8000 ---p 00004000 fe:00 272827 /usr/lib/evolution/2.30/plugins/liborg-gnome-plugin-manager.so 7f5599fd8000-7f5599fd9000 rw-p 00004000 fe:00 272827 /usr/lib/evolution/2.30/plugins/liborg-gnome-plugin-manager.so 7f5599fd9000-7f5599fdc000 r-xp 00000000 fe:00 305018 /usr/lib/evolution/2.30/plugins/liborg-gnome-mailing-list-actions.so 7f5599fdc000-7f559a1dc000 ---p 00003000 fe:00 305018 /usr/lib/evolution/2.30/plugins/liborg-gnome-mailing-list-actions.so 7f559a1dc000-7f559a1dd000 rw-p 00003000 fe:00 305018 /usr/lib/evolution/2.30/plugins/liborg-gnome-mailing-list-actions.so 7f559a1dd000-7f559a1e5000 r-xp 00000000 fe:00 305011 /usr/lib/evolution/2.30/plugins/liborg-gnome-mail-to-task.so 7f559a1e5000-7f559a3e5000 ---p 00008000 fe:00 305011 /usr/lib/evolution/2.30/plugins/liborg-gnome-mail-to-task.so 7f559a3e5000-7f559a3e6000 rw-p 00008000 fe:00 305011 /usr/lib/evolution/2.30/plugins/liborg-gnome-mail-to-task.so 7f559a3e6000-7f559a3ea000 r-xp 00000000 fe:00 272815 /usr/lib/evolution/2.30/plugins/liborg-gnome-mark-all-read.so 7f559a3ea000-7f559a5ea000 ---p 00004000 fe:00 272815 /usr/lib/evolution/2.30/plugins/liborg-gnome-mark-all-read.so 7f559a5ea000-7f559a5eb000 rw-p 00004000 fe:00 272815 /usr/lib/evolution/2.30/plugins/liborg-gnome-mark-all-read.so 7f559a5eb000-7f559a5f1000 r-xp 00000000 fe:00 280668 /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-xpm.so 7f559a5f1000-7f559a7f1000 ---p 00006000 fe:00 280668 /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-xpm.so 7f559a7f1000-7f559a7f2000 rw-p 00006000 fe:00 280668 /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-xpm.so 7f559a7f2000-7f559a7f3000 ---p 00000000 00:00 0 7f559a7f3000-7f559aff3000 rw-p 00000000 00:00 0 7f559aff3000-7f559aff4000 ---p 00000000 00:00 0 7f559aff4000-7f559b7f4000 rw-p 00000000 00:00 0 7f559b7f4000-7f559b7fb000 r-xp 00000000 fe:00 305012 /usr/lib/evolution/2.30/plugins/liborg-gnome-email-custom-header.so 7f559b7fb000-7f559b9fa000 ---p 00007000 fe:00 305012 /usr/lib/evolution/2.30/plugins/liborg-gnome-email-custom-header.so 7f559b9fa000-7f559b9fb000 rw-p 00006000 fe:00 305012 /usr/lib/evolution/2.30/plugins/liborg-gnome-email-custom-header.soAbandon
Just tested 2.30.3, and I cannot reproduce it.
Thanks for the quick update, Julien. What was the previous version, where you got this issue, please? I would like to investigate why this happened, to ensure it's really fixed in later version, thus if you would be able to downgrade to that previous version and do the below test runs, then it'll be great. Please install also debug info packages for evolution and evolution-data-server before running these tests, because without them the backtrace will be unusable. Test 0) ensure you can reproduce the issue even after downgrade. Test 1) Run evolution under gdb and reproduce the crash; You can run evolution like this $ gdb evolution --ex r --ex "t a a bt" --ex q and then reproduce the crash. When it stops it should provide a bactrace of the crash, which I would like to ask you to upload here. Basically everything on console after gdb invocation up to the quit of gdb. Only make sure it'll not contain any sensitive data, like email addresses, server addresses, passwords and such. Test 2) Run evolution under valgrind; It's easier than test 1, because it'll not nee any interaction on your side, like gdb, only run evolution like this: $ valgrind --num-callers=50 evolution &>log1.txt Valgrind usually prevents crashing on invalid memory usage and reports errors on console, thus if you do steps for a reproducer and it'll not crash, then just close evolution and look into the log1.txt file, whether valgrind found any invalid read or write. If so, please attach here the valgrind log too. Test 3) Run evolution under valgrind slightly tuned; The command is very similar like in the previous test, only here it's influencing GSlice memory allocations, which sometimes hides issues (in test 2). The command is: $ G_SLICE=always-malloc valgrind --num-callers=50 evolution &>log2.txt You probably know, but I'm mentioning here anyway: running Evolution under gdb is pretty quick, but under valgrind it's very slow, due to all the checks on memory done by valgrind, thus do not be scared of slowness and CPU usage with test 2 and test 3.
I was using 2.30.2. I'll downgrade and will test under gdb and valgrind ASAP.
(In reply to comment #37) > I was using 2.30.2. > > I'll downgrade and will test under gdb and valgrind ASAP. any news?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!