Bug 635590 – Crash on account re-enable

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 635590 - Crash on account re-enable


Summary:	Crash on account re-enable


Status:	RESOLVED FIXED

Product:	Evolution Exchange
Classification:	Deprecated
Component:	Connector
Version:	2.32.x
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	Connector Maintainer
QA Contact:	Ximian Connector QA

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2010-11-23 07:44 UTC by Milan Crha
Modified:	2011-01-27 11:37 UTC

See Also:
GNOME target:	---
GNOME version:	---

Attachments
eex patch (1.60 KB, patch) 2011-01-27 11:35 UTC, Milan Crha	committed	Details \| Review

Description Milan Crha 2010-11-23 07:44:50 UTC

Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=656007

abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: evolution
component: evolution
crash_function: __strcmp_ssse3
executable: /usr/bin/evolution
kernel: 2.6.35.6-48.fc14.i686
package: evolution-2.32.0-2.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1290458640
uid: 500

How to reproduce
-----
1. try to synchronize evolution with exchange 2010

Core was generated by `evolution'.
Program terminated with signal 11, Segmentation fault.

+ Trace 224796

Thread 13 (Thread 9564)

#0 message_queue_prepare
at egg-dbus.c line 56
#1 g_main_context_prepare
at gmain.c line 2469
#2 g_main_context_iterate
at gmain.c line 2760
#3 g_main_loop_run
at gmain.c line 2988
#4 IA__gtk_main
at gtkmain.c line 1237
#5 main
at main.c line 671

Thread 1 (Thread 9621)

#0 __strcmp_ssse3
from /lib/libc.so.6
#1 check_equal
at camel-url.c line 687
#2 camel_url_equal
at camel-url.c line 695
#3 is_same_ed
at camel-exchange-utils.c line 122
#4 get_data_for_service
at camel-exchange-utils.c line 168
#5 camel_exchange_utils_connect
at camel-exchange-utils.c line 2113
#6 exchange_store_connect
at camel-exchange-store.c line 356
#7 camel_service_connect
at camel-service.c line 326
#8 camel_exchange_store_connected
at camel-exchange-store.c line 821
#9 exchange_store_get_folder_info
at camel-exchange-store.c line 518
#10 camel_store_get_folder_info
at camel-store.c line 1122
#11 folder_tree_get_folder_info__exec
at em-folder-tree.c line 201
#12 mail_msg_proxy
at mail-mt.c line 469
#13 g_thread_pool_thread_proxy
at gthreadpool.c line 319
#14 g_thread_create_proxy
at gthread.c line 1897
#15 start_thread
from /lib/libpthread.so.0
#16 clone
from /lib/libc.so.6

Comment 1 Milan Crha 2011-01-27 11:35:15 UTC

Created attachment 179422 [details] [review]
eex patch

for evolution-exchange;

I was able to reproduce something very close to this. My steps are:
a) run evolution in offline with eex account disabled
b) enable eex account
c) wait till everything is initialized (no operation lefts in status bar)
d) disable eex account
e) wait till everything is initialized (no operation lefts in status bar)
f) enable eex account

The this is that the ExchangeData structure wasn't removed from the internal list of connections when the CamelExchangeService was freed.

Comment 2 Milan Crha 2011-01-27 11:37:53 UTC

Created commit 4b30fc3 in eex master (2.91.6+)