evolution crashed with SIGSEGV in g_slice_alloc()

Bug #575204 reported by xlazarus on 2010-05-04
38
This bug affects 7 people
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: evolution

Evolution is running a time without troubles an d then suddenly it crashes!
This happens when it's running alone AND when an bunch of other programs are running the same time.
The same thing happens with some others programs like Vuze ... crashes silently in background.

Used Version:
Description: Ubuntu 10.04 LTS
Release: 10.04
amd 64 Bit
Grafics: nvidia

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: evolution 2.28.3-0ubuntu9
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Tue May 4 16:31:14 2010
ExecutablePath: /usr/bin/evolution
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64 (20100419.1)
ProcCmdline: evolution
ProcEnviron:
 SHELL=/bin/bash
 LANG=de_AT.utf8
SegvAnalysis:
 Segfault happened at: 0x7fe64b5fc3a4 <g_slice_alloc+292>: mov (%rdx),%rcx
 PC (0x7fe64b5fc3a4) ok
 source "(%rdx)" (0x0000001f) not located in a known VMA region (needed readable region)!
 destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evolution
StacktraceTop:
 g_slice_alloc () from /lib/libglib-2.0.so.0
 g_slice_alloc0 () from /lib/libglib-2.0.so.0
 ?? () from /usr/lib/libpango-1.0.so.0
 pango_itemize_with_base_dir ()
 ?? () from /usr/lib/libpango-1.0.so.0
Title: evolution crashed with SIGSEGV in g_slice_alloc()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

xlazarus (xlazarus) wrote :
visibility: private → public

StacktraceTop:
 IA__g_slice_alloc (mem_size=64)
 IA__g_slice_alloc0 (mem_size=16)
 itemize_state_process_run (state=0x7fffb73354d0)
 pango_itemize_with_base_dir (
 pango_layout_check_lines (layout=0x28b6710)

Changed in evolution (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in evolution (Ubuntu):
status: New → Incomplete
xlazarus (xlazarus) wrote :
Changed in evolution (Ubuntu):
status: Incomplete → Confirmed
Pedro Villavicencio (pedro) wrote :

Is this still an issue with Natty?

Changed in evolution (Ubuntu):
status: Confirmed → Incomplete
Launchpad Janitor (janitor) wrote :

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

Changed in evolution (Ubuntu):
status: Incomplete → Expired
Nick Jenkins (nickpj) wrote :

I don't think I've seen this on Natty (i.e. Evolution 2.32.2), but it only occurred occasionally under earlier versions, thus making it hard to be certain. Given that I haven't seen it after some months on this version, I'd tentatively say that it's most probably fixed, and marking it as expired is probably the way to go.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers