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 789461 - Invalid read valgrind error when freeing event
Invalid read valgrind error when freeing event
Status: RESOLVED OBSOLETE
Product: gnome-calendar
Classification: Applications
Component: Backend
3.26.x
Other Linux
: Normal normal
: 3.26
Assigned To: GNOME Calendar maintainers
GNOME Calendar maintainers
Depends on:
Blocks:
 
 
Reported: 2017-10-25 08:39 UTC by Sebastien Bacher
Modified: 2017-11-24 22:43 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sebastien Bacher 2017-10-25 08:39:05 UTC
Using 3.26.2 on Ubuntu 17.10 after adding a google account and opening the preference the valgrind log has this invalid read error

==9231== Invalid read of size 1
==9231==    at 0x7FD7C40: __strcmp_sse2_unaligned (strcmp-sse2-unaligned.S:24)
==9231==    by 0x6FC91D8: g_str_equal (ghash.c:1852)
==9231==    by 0x6FC80B6: g_hash_table_lookup_node (ghash.c:400)
==9231==    by 0x6FC80B6: g_hash_table_remove_internal (ghash.c:1359)
==9231==    by 0x142124: gcal_event_finalize (gcal-event.c:467)
==9231==    by 0x6D4FEB1: g_object_unref (gobject.c:3330)
==9231==    by 0x140E7A: gcal_event_widget_finalize (gcal-event-widget.c:534)
==9231==    by 0x6D4FEB1: g_object_unref (gobject.c:3330)
==9231==    by 0x5492B0D: gtk_container_destroy (gtkcontainer.c:1700)
==9231==    by 0x6D4AF9C: g_closure_invoke (gclosure.c:804)
==9231==    by 0x6D5DE51: signal_emit_unlocked_R (gsignal.c:3751)
==9231==    by 0x6D664B4: g_signal_emit_valist (gsignal.c:3391)
==9231==    by 0x6D66ECE: g_signal_emit (gsignal.c:3447)
==9231==  Address 0x33fcb5f0 is 64 bytes inside a block of size 152 free'd
==9231==    at 0x4C30D3B: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==9231==    by 0x753E3DC: icalproperty_free (icalproperty.c:191)
==9231==    by 0x7537871: icalcomponent_free (icalcomponent.c:205)
==9231==    by 0x72CEF74: free_icalcomponent (e-cal-component.c:351)
==9231==    by 0x72D0CA8: cal_component_finalize (e-cal-component.c:367)
==9231==    by 0x6D4FEB1: g_object_unref (gobject.c:3330)
==9231==    by 0x1571A0: component_data_free (e-cal-data-model.c:206)
==9231==    by 0x6FC7AEE: g_hash_table_insert_node (ghash.c:997)
==9231==    by 0x6FC7F6A: g_hash_table_insert_internal (ghash.c:1235)
==9231==    by 0x15762F: cal_data_model_process_added_component (e-cal-data-model.c:893)
==9231==    by 0x157F18: cal_data_model_notify_recurrences_cb (e-cal-data-model.c:1027)
==9231==    by 0x6FDA8A2: g_timeout_dispatch (gmain.c:4633)
==9231==  Block was alloc'd at
==9231==    at 0x4C2FB0F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==9231==    by 0x754B35C: icalvalue_new_impl (icalvalue.c:46)
==9231==    by 0x754B4DF: icalvalue_new_clone (icalvalue.c:71)
==9231==    by 0x753E473: icalproperty_new_clone (icalproperty.c:104)
==9231==    by 0x7537FAF: icalcomponent_new_clone (icalcomponent.c:164)
==9231==    by 0x159788: cal_data_model_process_modified_or_added_objects (e-cal-data-model.c:1233)
==9231==    by 0x6D4E041: g_cclosure_marshal_VOID__POINTERv (gmarshal.c:2026)
==9231==    by 0x6D4B1D5: _g_closure_invoke_va (gclosure.c:867)
==9231==    by 0x6D6679E: g_signal_emit_valist (gsignal.c:3300)
==9231==    by 0x6D66ECE: g_signal_emit (gsignal.c:3447)
==9231==    by 0x72CD82B: cal_client_view_emit_objects_added_idle_cb (e-cal-client-view.c:215)
==9231==    by 0x6FD9E24: g_main_dispatch (gmain.c:3148)
==9231==    by 0x6FD9E24: g_main_context_dispatch (gmain.c:3813)
Comment 1 Sebastien Bacher 2017-10-25 08:39:37 UTC
Ubuntu users reports bug in libical functions, could be due to this error

example
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1725951
Comment 2 Georges Basile Stavracas Neto 2017-11-24 22:43:41 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-calendar/issues/207.