Bug 587057 – Crash in get_folder_info_offline at camel-imap-store.c line 2802

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 587057 - Crash in get_folder_info_offline at camel-imap-store.c line 2802


Summary:	Crash in get_folder_info_offline at camel-imap-store.c line 2802


Status:	RESOLVED OBSOLETE

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

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

URL:
Whiteboard:	evolution[disk-summary]

Duplicates:	616148 (view as bug list)
Depends on:
Blocks:

Reported:	2009-06-26 14:59 UTC by davide.rossetti
Modified:	2013-08-03 12:41 UTC

See Also:
GNOME target:	---
GNOME version:	2.27/2.28

Description davide.rossetti 2009-06-26 14:59:59 UTC

What were you doing when the application crashed?
just launched the application


Distribution: Fedora release 11 (Leonidas)
Gnome Release: 2.26.2 2009-06-01 (Red Hat, Inc)
BugBuddy Version: 2.26.0

System: Linux 2.6.29.4-167.fc11.x86_64 #1 SMP Wed May 27 17:27:08 EDT 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10601901
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Fedora
GTK+ Modules: canberra-gtk-module, pk-gtk-module, gnomebreakpad

Memory status: size: 920072192 vsize: 920072192 resident: 24358912 share: 17768448 rss: 24358912 rss_rlim: 18446744073709551615
CPU usage: start_time: 1246028361 rtime: 22 utime: 18 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[?1034h[Thread debugging using libthread_db enabled]
[New Thread 0x7fe01d7ee910 (LWP 22267)]
[New Thread 0x7fe01e1ef910 (LWP 22266)]
[New Thread 0x7fe01ebf0910 (LWP 22265)]
[New Thread 0x7fe01f819910 (LWP 22264)]
[New Thread 0x7fe02021a910 (LWP 22263)]
0x00000030c1e0e9dd in __libc_waitpid (pid=22268, stat_loc=<value optimized out>, options=0)
    at ../sysdeps/unix/sysv/linux/waitpid.c:41
41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);
Current language:  auto; currently minimal

+ Trace 216203

Thread 2 (Thread 0x7fe01d7ee910 (LWP 22267))

#0 __lll_lock_wait
at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S line 136
#1 _L_lock_949
from /lib64/libpthread.so.0
#2 __pthread_mutex_lock
at pthread_mutex_lock.c line 61
#3 <signal handler called>
#4 get_folder_info_offline
at camel-imap-store.c line 2802
#5 get_folder_info
at camel-imap-store.c line 2768
#6 camel_store_get_folder_info
at camel-store.c line 894
#7 get_folderinfo_exec
at mail-ops.c line 1075
#8 mail_msg_proxy
at mail-mt.c line 520
#9 g_thread_pool_thread_proxy
at gthreadpool.c line 265
#10 g_thread_create_proxy
at gthread.c line 635
#11 start_thread
at pthread_create.c line 297
#12 clone
at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 112
#13 ??



----------- .xsession-errors (265 sec old) ---------------------
RtApiAlsa: underrun detected.
RtApiAlsa: underrun detected.
RtApiAlsa: underrun detected.
RtApiAlsa: underrun detected.
RtApiAlsa: underrun detected.
--------------------------------------------------

Comment 1 Milan Crha 2009-07-15 12:24:12 UTC

Thread 2

+ Trace 216457

#3 <signal handler called>
#4 get_folder_info_offline
at camel-imap-store.c line 2802
#5 get_folder_info
at camel-imap-store.c line 2768
#6 camel_store_get_folder_info
at camel-store.c line 894
#7 get_folderinfo_exec
at mail-ops.c line 1075
#8 mail_msg_proxy
at mail-mt.c line 520
#4 <signal handler called>
#5 get_folder_info_offline
at camel-imap-store.c line 2802
#6 get_folder_info
at camel-imap-store.c line 2768
#7 camel_store_get_folder_info
at camel-store.c line 894
#8 migrate_to_db
at em-migrate.c line 3018
#9 em_migrate


Srag, I think you did something in the migrate code, or maybe someone else, I'm not sure now. Do not you know?

Comment 2 Srinivasa Ragavan 2009-08-19 05:35:45 UTC

Hmm, I dont remember if I did anything recent in the migration code. Lemme analyze it though

Comment 3 Srinivasa Ragavan 2009-08-19 07:30:44 UTC

This is neither the disk summary migration related nor any other migration. Some genuine imap issue. The namespace uri is corrupted. Valgrind might help a bit.

Comment 4 Akhil Laddha 2009-11-27 05:40:40 UTC

Did you get similar crash any time later ?  Can you please try in 2.28.x and report back, thanks.

Comment 5 Tobias Mueller 2010-01-13 04:26:23 UTC

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!

Comment 6 Fabio Durán Verdugo 2010-04-19 23:41:06 UTC

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

Comment 7 Fabio Durán Verdugo 2010-04-19 23:41:38 UTC

last dup in 2.28

Comment 8 André Klapper 2013-08-03 09:58:19 UTC

All reports from before 2.28. Does this crash still happen in 3.8 or 3.6? 
Code base has changed a lot, hence asking.

Comment 9 Matthew Barnes 2013-08-03 12:41:31 UTC

The legacy IMAP backend is gone as of 3.8, so closing this as OBSOLETE.