Ubuntu
evolution-data-server package

evolution-source-registry crashed with SIGSEGV in magazine_chain_pop_head()

Bug #1195662 reported by Michael Blennerhassett
158
This bug affects 30 people
Affects Status Importance Assigned to Milestone
evolution-data-server (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Crashed at login

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: evolution-data-server 3.8.3-0ubuntu4
ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7
Uname: Linux 3.9.0-7-generic x86_64
ApportVersion: 2.10.2-0ubuntu2
Architecture: amd64
Date: Fri Jun 28 19:52:38 2013
ExecutablePath: /usr/lib/evolution/evolution-source-registry
InstallationDate: Installed on 2013-06-22 (6 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130621)
MarkForUpload: True
ProcCmdline: /usr/lib/evolution/evolution-source-registry
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_AU:en
 LANG=en_AU.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f6da1c4375a <g_slice_alloc+154>: mov 0x8(%rdx),%rbx
 PC (0x7f6da1c4375a) ok
 source "0x8(%rdx)" (0x15c11207f) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: evolution-data-server
StacktraceTop:
 g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_bytes_new_with_free_func () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_variant_new_byte () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: evolution-source-registry crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Michael Blennerhassett (mjblenner) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 magazine_chain_pop_head (magazine_chunks=0x7f6d880008f0) at /build/buildd/glib2.0-2.37.3/./glib/gslice.c:541
 thread_memory_magazine1_alloc (tmem=<optimized out>, ix=2) at /build/buildd/glib2.0-2.37.3/./glib/gslice.c:848
 g_slice_alloc (mem_size=mem_size@entry=40) at /build/buildd/glib2.0-2.37.3/./glib/gslice.c:1007
 g_bytes_new_with_free_func (data=0x7f6d8800b1b0, size=size@entry=1, free_func=0x7f6da1c2dc40 <g_free>, user_data=0x7f6d8800b1b0) at /build/buildd/glib2.0-2.37.3/./glib/gbytes.c:176
 g_bytes_new_take (data=<optimized out>, size=size@entry=1) at /build/buildd/glib2.0-2.37.3/./glib/gbytes.c:124

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-data-server (Ubuntu):
importance: Undecided → Medium
summary: - evolution-source-registry crashed with SIGSEGV in g_slice_alloc()
+ evolution-source-registry crashed with SIGSEGV in
+ magazine_chain_pop_head()
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
Apport retracing service (apport)
tags: added: trusty
Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :

I have just raised Bug #1527495 which was initially suggested as a possible duplicate of this bug and Bug #1235177. Now that apport has done its thing my new bug has been marked as a duplicate of bug #1279108 which could suggest that this bug is also a duplicate of that one.

Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :

So I have tripped over the same problem again, but this time only Bug #1195662 and Bug #1235177 were offered as suggestions. Bug #1527495 that I raised a while ago was not seen as a likely similarity.

It seems that I am able to periodically reproduce a problem, whether it is one of the three bugs listed above or the possibly mythical bug #1279108 I cannot say. However if there are any investigative steps I can take or work arounds to try please do get in touch.

Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :

Seen again today.

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

Other bug subscribers

Remote bug watches

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