Bug 780894 – Crash under e_cal_recur_generate_instances()

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 780894 - Crash under e_cal_recur_generate_instances()


Summary:	Crash under e_cal_recur_generate_instances()


Status:	RESOLVED NOTGNOME

Product:	evolution
Classification:	Applications
Component:	Calendar
Version:	3.22.x (obsolete)
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	evolution-calendar-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

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

Reported:	2017-04-04 09:27 UTC by Christian Gogolin
Modified:	2018-01-17 09:06 UTC

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

Description Christian Gogolin 2017-04-04 09:27:39 UTC

My Evolution 3.22.6 from Debian just crashed with the following segfault:

Thread 5266 "pool" received signal SIGSEGV, Segmentation fault.

+ Trace 237324

Thread 140733059168000 (LWP 29251)

#0 icaltimezone_get_utc_offset
#1 icaltimezone_convert_time
#2 icaltime_as_timet_with_zone
#3 e_cal_recur_generate_instances_sync
#4 e_cal_recur_generate_instances
#5 0x00007fffef068b16 in
#6 e_cal_client_generate_instances_for_object_sync
#7 cal_data_model_expand_recurrences_thread
at e-cal-data-model.c line 1114
#8 cal_data_model_internal_thread_job_func
at e-cal-data-model.c line 393
#9 g_thread_pool_thread_proxy
at ././glib/gthreadpool.c line 307
#10 g_thread_proxy
at ././glib/gthread.c line 784
#11 start_thread
at pthread_create.c line 333
#12 clone
at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 105
#1 icaltimezone_convert_time
from /usr/lib/x86_64-linux-gnu/libical.so.2
#2 icaltime_as_timet_with_zone
from /usr/lib/x86_64-linux-gnu/libical.so.2
#3 e_cal_recur_generate_instances_sync
from /usr/lib/x86_64-linux-gnu/libecal-1.2.so.19
#4 e_cal_recur_generate_instances
from /usr/lib/x86_64-linux-gnu/libecal-1.2.so.19
#5 ??
from /usr/lib/x86_64-linux-gnu/libecal-1.2.so.19
#6 e_cal_client_generate_instances_for_object_sync
from /usr/lib/x86_64-linux-gnu/libecal-1.2.so.19
#7 cal_data_model_expand_recurrences_thread
at e-cal-data-model.c line 1114
#8 cal_data_model_internal_thread_job_func
at e-cal-data-model.c line 393
#9 g_thread_pool_thread_proxy
at ././glib/gthreadpool.c line 307
#10 g_thread_proxy
at ././glib/gthread.c line 784
#11 start_thread
at pthread_create.c line 333
#12 clone
at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 105

Comment 1 Milan Crha 2017-04-05 10:38:29 UTC

Thanks for a bug report. I guess this is similar to bug #634294, which had been fixed before 3.22.x. The issue can be still the same, using an icaltimezone object which had been freed.

Do you have any reproducer, please? What is the calendar type you see it with, please? (local, CalDAV, ...)

Comment 2 Christian Gogolin 2017-04-05 11:59:21 UTC

I don't know how to reproduce it. It just happened while I was using Evolution normally, though over a pretty choppy internet connection. I mostly have CalDAV calendars.

Comment 3 Milan Crha 2017-10-03 13:21:48 UTC

Good news, sort of. Opening Evolution in the calendar Month View today, with enabled On This Computer, CalDAV, Google and On The Web calendars, causes this crash. I sent a message to libical mailing list for an advice on what would be the best to do to avoid it:
http://lists.infradead.org/pipermail/libical-devel/2017-October/000765.html

Comment 4 Milan Crha 2018-01-12 07:52:20 UTC

This is [1], whitch landed in libical 3.0.0, with some follow up fixes included in libical 3.0.1.

[1] https://github.com/libical/libical/issues/319

Comment 5 Milan Crha 2018-01-17 09:06:00 UTC

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