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 673197 - Calendar backend crashing when opening an entry several times for editing
Calendar backend crashing when opening an entry several times for editing
Status: RESOLVED WONTFIX
Product: evolution-kolab
Classification: Other
Component: converter
3.4.x
Other Linux
: Normal major
: ---
Assigned To: Christian Hilberg
Evolution Kolab maintainer(s)
gnome[unmaintained]
: 669068 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2012-03-30 16:43 UTC by Christian Hilberg
Modified: 2018-06-30 14:38 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Christian Hilberg 2012-03-30 16:43:41 UTC 
The calendar backend crashes if the edit popup for an event is closed and opened several times, or if a second event is added to a day in the month view.

evolution-calendar-factory backtrace:

---
(gdb) bt

+ Trace 229981

  • #0 __kernel_vsyscall
  • #1 __GI_raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
  • #2 __GI_abort
    at abort.c line 91
  • #3 __libc_message
    at ../sysdeps/unix/sysv/linux/libc_fatal.c line 201
  • #4 malloc_printerr
    at malloc.c line 5007
  • #5 icalmemory_free_ring_byval
    from /usr/lib/libical.so.0
  • #6 ??
    from /usr/lib/libical.so.0
  • #7 __nptl_deallocate_tsd
    at pthread_create.c line 156
  • #8 start_thread
    at pthread_create.c line 315
  • #9 clone
    at ../sysdeps/unix/sysv/linux/i386/clone.S line 130 






Comment 1


Christian Hilberg





          2012-03-30 16:45:06 UTC
        



Confirmed.

Issue shows with libical 0.48, but does not show with libical 0.44.
Looks like a change in libical memory management.






Comment 2


Christian Hilberg





          2012-04-02 10:42:40 UTC
        



The issue *might* be related to this one:

http://sourceforge.net/mailarchive/message.php?msg_id=29069293

evolution-kolab does some timezone handling, so it could be a related issue. Needs further invesitgation, though (from the gdb backtraces it is currently not clear whether the evolution-kolab crash described here is actually caused by timezone handling).






Comment 3


Christian Hilberg





          2012-04-02 10:47:51 UTC
        



https://bugs.launchpad.net/ubuntu/+source/libical/+bug/956843 contains some more, possibly related info.






Comment 4


Christian Hilberg





          2012-04-12 19:32:13 UTC
        



Commit 9d0fd8c600eac78019592267b5742555dbbb2d85 in evolution-kolab Git master has a partial fix for the issue. The crash no longer occurs, but we may be leaking timezone bits. This fix, though partial, will be included in evolution-kolab 3.4.1.

Note that if you're using libical0.48, you need an updated version which at least contains the workaround mentioned in http://sourceforge.net/mailarchive/message.php?msg_id=29069293, otherwise the crash will still occur.

Once libical0.48 gets fixed upstream, we need to revisit this issue and see whether we're actually leaking (and if so, complete this partial fix). I'm thus leaving this bug open.






Comment 5


Milan Crha





          2012-04-27 08:59:48 UTC
        



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






Comment 6


André Klapper





          2018-06-30 14:38:20 UTC
        



evolution-kolab is not under active development anymore and has not seen code changes for more than five years.
Its codebase has been archived: https://gitlab.gnome.org/Archive/evolution-kolab/commits/master

Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (or rather transfer the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active development again.