evolution-calendar-factory crashed with SIGSEGV in tcache_get()

Bug #1844100 reported by Jean-Baptiste Lallement
28
This bug affects 4 people
Affects Status Importance Assigned to Milestone
evolution-data-server (Ubuntu)
Expired
Low
Unassigned

Bug Description

it crashed

ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: evolution-data-server 3.33.91-3
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 16 09:53:33 2019
ExecutablePath: /usr/libexec/evolution-calendar-factory
InstallationDate: Installed on 2013-09-03 (2203 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcCmdline: /usr/libexec/evolution-calendar-factory
ProcEnviron:
 LANG=fr_FR.UTF-8
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7f7b13f583ae <__GI___libc_malloc+286>: mov (%r8),%rsi
 PC (0x7f7b13f583ae) ok
 source "(%r8)" (0x7f7a00000002) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: evolution-data-server
StacktraceTop:
 tcache_get (tc_idx=<optimized out>) at malloc.c:2937
 __GI___libc_malloc (bytes=40) at malloc.c:3051
 pvl_newlist () at /usr/lib/x86_64-linux-gnu/libical.so.3
 () at /usr/lib/x86_64-linux-gnu/libical.so.3
 i_cal_component_new () at /usr/lib/x86_64-linux-gnu/libical-glib.so.3
Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get()
UpgradeStatus: Upgraded to eoan on 2018-01-26 (597 days ago)
UserGroups: adm autopilot cdrom dip docker libvirt lpadmin lxd plugdev sambashare stapdev stapsys stapusr sudo
separator:

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 tcache_get (tc_idx=<optimized out>) at malloc.c:2937
 __GI___libc_malloc (bytes=bytes@entry=40) at malloc.c:3051
 pvl_newlist () at ./src/libical/pvl.c:65
 icalcomponent_new_impl (kind=kind@entry=ICAL_VEVENT_COMPONENT) at ./src/libical/icalcomponent.c:104
 icalcomponent_new (kind=kind@entry=ICAL_VEVENT_COMPONENT) at ./src/libical/icalcomponent.c:114

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in evolution-data-server (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in evolution-data-server (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Changed in evolution-data-server (Ubuntu):
importance: Medium → Low
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for evolution-data-server (Ubuntu) because there has been no activity for 60 days.]

Changed in evolution-data-server (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.