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 566874 - Evolution crashed while fetching summary in a MAPI folder
Evolution crashed while fetching summary in a MAPI folder
Status: RESOLVED FIXED
Product: evolution-mapi
Classification: Applications
Component: Mail
0.26.x
Other All
: High critical
: ---
Assigned To: Johnny Jacob
evolution-mapi-maint
: 568523 575951 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-01-07 08:41 UTC by Kandepu Prasad
Modified: 2010-06-15 18:01 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Kandepu Prasad 2009-01-07 08:41:37 UTC
Steps to reproduce:
1. Clicked on a MAPI folder having around 6172 mails in it
2. Status bar showed "Fetching summary ...."
3. It crashed with below traces.


Stack trace:
(evolution.bin:7667): camel-mapi-provider-WARNING **: Unable to load summary no such table: Mailbox - KVBV Prasad/Customer/Dave/City_of_largo

[New Thread 0xb447ab90 (LWP 7944)]

exchange-mapi-connection.c(2206): Entering exchange_mapi_set_flags libexchangemapi-Message: exchange-mapi-connection.c(2208): exchange_mapi_set_flags: lock(connect_lock)
libexchangemapi-Message: exchange-mapi-connection.c(2245): exchange_mapi_set_flags: unlock(connect_lock)

exchange-mapi-connection.c(2247): Leaving exchange_mapi_set_flags 
exchange-mapi-connection.c(1007): Entering exchange_mapi_connection_fetch_items: folder-id C08E1CDE08010001 libexchangemapi-Message: exchange-mapi-connection.c(1009): exchange_mapi_connection_fetch_items: lock(connect_lock)
[Thread 0xaead1b90 (LWP 7943) exited]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb447ab90 (LWP 7944)]
cast_mapi_SPropValue (mapi_sprop=0x0, sprop=0xcb56e30) at libmapi/property.c:426
426	libmapi/property.c: No such file or directory.
	in libmapi/property.c
(gdb) t a a bt

Thread 64 (Thread 0xb447ab90 (LWP 7944))

  • #0 cast_mapi_SPropValue
    at libmapi/property.c line 426
  • #1 exchange_mapi_connection_fetch_items
    at exchange-mapi-connection.c line 1168
  • #2 mapi_refresh_folder
    at camel-mapi-folder.c line 639
  • #3 mapi_refresh_info
    at camel-mapi-folder.c line 142
  • #4 camel_folder_refresh_info
    at camel-folder.c line 328
  • #5 refresh_folder_exec
    at mail-ops.c line 1658
  • #6 mail_msg_proxy
    at mail-mt.c line 520
  • #7 g_thread_pool_thread_proxy
    at gthreadpool.c line 265
  • #8 g_thread_create_proxy
    at gthread.c line 635
  • #9 start_thread
    at pthread_create.c line 297
  • #10 clone
    at ../sysdeps/unix/sysv/linux/i386/clone.S line 130

Thread 64 (Thread 0xb447ab90 (LWP 7944))

  • #0 cast_mapi_SPropValue
    at libmapi/property.c line 426
  • #1 exchange_mapi_connection_fetch_items
    at exchange-mapi-connection.c line 1168
  • #2 mapi_refresh_folder
    at camel-mapi-folder.c line 639
  • #3 mapi_refresh_info
    at camel-mapi-folder.c line 142
  • #4 camel_folder_refresh_info
    at camel-folder.c line 328
  • #5 refresh_folder_exec
    at mail-ops.c line 1658
  • #6 mail_msg_proxy
    at mail-mt.c line 520
  • #7 g_thread_pool_thread_proxy
    at gthreadpool.c line 265
  • #8 g_thread_create_proxy
    at gthread.c line 635
  • #9 start_thread
    at pthread_create.c line 297
  • #10 clone
    at ../sysdeps/unix/sysv/linux/i386/clone.S line 130



Other information:
MAPI rpms: evolution-mapi-provider-0.1-5.5, evolution-mapi-provider-debuginfo-0.1-5.5
Buildinfo: sled11 RC1 with updates from kirk site as on today.
Comment 1 Johnny Jacob 2009-01-19 09:17:31 UTC
Happens in trunk.

Reason : Memory allocator runs out of memory. A lot is leaked here !
Comment 2 Johnny Jacob 2009-01-26 19:31:36 UTC
Depends on http://trac.openchange.org/ticket/128
Comment 3 Akhil Laddha 2009-03-20 11:00:22 UTC
*** Bug 575951 has been marked as a duplicate of this bug. ***
Comment 4 Akhil Laddha 2009-04-29 05:57:39 UTC
Crash is still valid with libmapi revision 1340, evolution-mapi revision 198

exchange-mapi-connection.c:1004: Entering exchange_mapi_connection_fetch_items: folder-id 9124020000000001 libexchangemapi-Message: exchange-mapi-connection.c:1006: exchange_mapi_connection_fetch_items: lock(connect_lock)
[Thread 0xab4edb90 (LWP 5579) exited]
[New Thread 0xab4edb90 (LWP 5582)]
[New Thread 0xa9cffb90 (LWP 5583)]
[Thread 0xa9cffb90 (LWP 5583) exited]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xaac06b90 (LWP 5580)]
cast_mapi_SPropValue (mapi_sprop=0x0, sprop=0x8c7b308) at libmapi/property.c:435
435	libmapi/property.c: No such file or directory.
	in libmapi/property.c
(gdb) t a a bt

Thread 36 (Thread 0xaac06b90 (LWP 5580))

  • #0 cast_mapi_SPropValue
    at libmapi/property.c line 435
  • #1 exchange_mapi_connection_fetch_items
    at exchange-mapi-connection.c line 1170
  • #2 mapi_refresh_folder
    at camel-mapi-folder.c line 747
  • #3 mapi_refresh_info
    at camel-mapi-folder.c line 154
  • #4 camel_folder_refresh_info
    at camel-folder.c line 349
  • #5 refresh_folder_exec
    at mail-ops.c line 1664
  • #6 mail_msg_proxy
    at mail-mt.c line 520
  • #7 g_thread_pool_thread_proxy
    at gthreadpool.c line 265
  • #8 g_thread_create_proxy
    at gthread.c line 635
  • #9 start_thread
    from /lib/libpthread.so.0
  • #10 clone
    from /lib/libc.so.6

Comment 5 Akhil Laddha 2010-03-02 05:39:54 UTC
After evolution-mapi dependency has been moved to libmapi 0.9, i don't seem to get crash.
Comment 6 Milan Crha 2010-06-15 18:01:15 UTC
*** Bug 568523 has been marked as a duplicate of this bug. ***