GNOME Bugzilla – Bug 676471
[abrt] Double free when sorting by date columns in calendar
Last modified: 2014-11-11 11:38:06 UTC
Moving this from a downstream bug report: https://bugzilla.redhat.com/show_bug.cgi?id=823348 [abrt] evolution-3.2.3-3.fc16: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) libreport version: 2.0.8 abrt_version: 2.0.7 backtrace_rating: 4 cmdline: evolution crash_function: icaltimezone_load_builtin_timezone executable: /usr/bin/evolution kernel: 3.3.5-2.fc16.i686.PAE reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) time: Mon 21 May 2012 08:44:16 AM MYT comment: :When switching to 'calendar', this crash occurs. :Reopening evolution leads to same problem (immediate crash). :Launching with: evolution --express works, and after closing, will open without --express. :Switching to calendar again results in a crash (either immediately or on first interaction). :Note: Using remote calendar via google. Core was generated by `evolution'. Program terminated with signal 11, Segmentation fault.
+ Trace 230247
Thread 2 (Thread 0xb7494b40 (LWP 2160))
Thread 1 (Thread 0xb77338c0 (LWP 2158))
Might be the same issue as described in bug #673197
Similar crash from evolution-data-server 3.6.1: https://bugzilla.redhat.com/show_bug.cgi?id=880864
+ Trace 231234
Thread 1 (Thread 0xb28eeb40 (LWP 10453))
Yet another downstream bug report from 3.12.7: https://bugzilla.redhat.com/show_bug.cgi?id=1158711 -------------------------------------------------------------------------------- I managed to reproduce this when the Tasks, Memos or Calendar tables (list view) are sorted by a date column, which are Created, Last Modified, Start Date, End Date, Due Date and Completed. I believe it's the cause, for which I'll use this bug report (there happened a double free, which could free anything in the memory).
Created commit 7af5d37 in evo master (3.13.8+) [1] Created commit ca64c26 in evo evolution-3-12 (3.12.8+) https://git.gnome.org/browse/evolution/commit/?id=7af5d37
*** Bug 739597 has been marked as a duplicate of this bug. ***