Bug 499975 – crash in camel_message_info_ptr at camel-folder-summary.c:2956

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 499975 - crash in camel_message_info_ptr at camel-folder-summary.c:2956


Summary:	crash in camel_message_info_ptr at camel-folder-summary.c:2956


Status:	RESOLVED OBSOLETE

Product:	evolution
Classification:	Applications
Component:	Mailer
Version:	2.22.x (obsolete)
Hardware:	Other All

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

URL:
Whiteboard:

Duplicates:	455329 503155 514320 528761 537384 539267 542431 543302 (view as bug list)
Depends on:
Blocks:

Reported:	2007-11-27 13:52 UTC by drstitch
Modified:	2009-01-20 00:04 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description drstitch 2007-11-27 13:52:09 UTC

Version: 2.10

What were you doing when the application crashed?
Nothing.  I came in this morning and the bug reporting tool was open.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 20:25:37 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 223588352 vsize: 223588352 resident: 122499072 share: 53731328 rss: 122499072 rss_rlim: 4294967295
CPU usage: start_time: 1196088062 rtime: 10922 utime: 10375 stime: 547 cutime:1 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1209186592 (LWP 28179)]
[New Thread -1324352624 (LWP 3672)]
[New Thread -1245389936 (LWP 1072)]
[New Thread -1230828656 (LWP 29333)]
[New Thread -1255892080 (LWP 28252)]
[New Thread -1211286640 (LWP 28249)]
0x00110402 in __kernel_vsyscall ()

+ Trace 179822

Thread 2 (Thread -1324352624 (LWP 3672))

#0 __kernel_vsyscall
#1 __lll_mutex_lock_wait
from /lib/libpthread.so.0
#2 _L_mutex_lock_79
from /lib/libpthread.so.0
#3 pthread_mutex_lock
from /lib/libpthread.so.0
#4 segv_redirect
at main.c line 417
#5 <signal handler called>
#6 camel_message_info_ptr
at camel-folder-summary.c line 2956
#7 message_info_save
at camel-folder-summary.c line 1906
#8 message_info_save
at camel-exchange-summary.c line 200
#9 camel_folder_summary_save
at camel-folder-summary.c line 717
#10 exchange_sync
at camel-exchange-folder.c line 1136
#11 camel_folder_sync
at camel-folder.c line 273
#12 store_sync
at camel-store.c line 643
#13 camel_store_sync
at camel-store.c line 665
#14 sync_store_exec
at mail-ops.c line 1484
#15 mail_msg_proxy
at mail-mt.c line 500
#16 g_thread_pool_thread_proxy
at gthreadpool.c line 265
#17 g_thread_create_proxy
at gthread.c line 594
#18 start_thread
from /lib/libpthread.so.0
#19 clone
from /lib/libc.so.6



----------- .xsession-errors (9 sec old) ---------------------
** Message: Response 1
xscreensaver-command: activating and locking.
warning: .dynamic section for "/lib/libselinux.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libldap-2.3.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/liblber-2.3.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------

Comment 1 Tobias Mueller 2007-12-02 15:20:03 UTC

This is a duplicate of 455329 but this one has a nice stacktrace. Setting NEW due to the amount of Dups.

Comment 2 Tobias Mueller 2007-12-02 15:20:59 UTC

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

Comment 3 André Klapper 2007-12-12 13:36:28 UTC

36 duplicates so far.

Comment 4 André Klapper 2007-12-29 12:02:10 UTC

only 2.10 bug duplicates from fedora 7 so far (except for bug 425978 from ubuntu 6.10).

@Tobias: while this report has a better trace, marking bug 455329 as a dup of this one does not copy all the CC entries, so we will not get a better trace here that easily.

Comment 5 Tobias Mueller 2008-02-26 23:34:59 UTC

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

Comment 6 Tobias Mueller 2008-02-26 23:35:34 UTC

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

Comment 7 Tobias Mueller 2008-06-16 21:36:20 UTC

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

Comment 8 Tobias Mueller 2008-06-16 21:36:52 UTC

Bug 537384 is on 2.22 and has a nice stacktrace.

Comment 9 Tobias Mueller 2008-06-26 15:30:06 UTC

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

Comment 10 Tobias Mueller 2008-07-11 17:24:41 UTC

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

Comment 11 Tobias Mueller 2008-07-11 17:24:46 UTC

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

Comment 12 Tobias Mueller 2008-07-20 21:54:20 UTC

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

Comment 13 Milan Crha 2008-09-10 14:55:17 UTC

This part has been rewritten in 2.24 where is db-summary used. Lowering severity. I will appreciate, if someone can try to let it crash in that or later version.
Also, from the duplicates it seems it's related to exchange backend only.

Comment 14 Tobias Mueller 2009-01-20 00:04:27 UTC

Seems to be OBSOLETE by now. Congrats :)