evolution crashed with SIGSEGV in g_slice_alloc()

Bug #584867 reported by Jens Friedrich
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: evolution

crashes while running in background...exact problem is not reproducable...probably in combination with spamassassin or clamav

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: evolution 2.28.3-0ubuntu9
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Mon May 24 11:09:50 2010
ExecutablePath: /usr/bin/evolution
ProcCmdline: evolution
ProcEnviron:
 SHELL=/bin/bash
 LANG=de_DE.utf8
SegvAnalysis:
 Segfault happened at: 0x40c8959: mov (%eax),%esi
 PC (0x040c8959) ok
 source "(%eax)" (0x00000071) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evolution
StacktraceTop:
 ?? () from /lib/libglib-2.0.so.0
 g_slice_alloc () from /lib/libglib-2.0.so.0
 g_slice_alloc0 () from /lib/libglib-2.0.so.0
 g_type_create_instance () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: evolution crashed with SIGSEGV in g_slice_alloc()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1461): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-terminal:2374): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed

Revision history for this message
Jens Friedrich (dj-jeff) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? () from /lib/libglib-2.0.so.0
 g_slice_alloc () from /lib/libglib-2.0.so.0
 g_slice_alloc0 () from /lib/libglib-2.0.so.0
 g_type_create_instance () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in evolution (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
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
visibility: private → public
Revision history for this message
Jens Friedrich (dj-jeff) wrote :

Just startet Valgrind described in the article.
Step "Perform any actions necessary to reproduce the crash." can't be done.
Can't reproduce because if it crashes, it crashes always with different behaviour. So I've added the log created until complete startup of evolution.

Hope, it helps too.

Revision history for this message
Jens Friedrich (dj-jeff) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

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

Other bug subscribers

Remote bug watches

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