totem crashed with SIGSEGV in magazine_chain_pop_head() from magazine_chain_prepare_fields() from magazine_cache_push_magazine() from thread_memory_magazine2_unload() from g_slice_free1()

Bug #1290378 reported by S. Neumann
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
totem (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I was just watching a movie with it and fast forwarded it, when totem crashed.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: totem 3.10.1-1ubuntu3
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Mar 10 14:44:09 2014
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2014-03-04 (6 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226)
ProcCmdline: totem /media/username/Movies/Movies/Shrek\ 3\ [en]/Shrek\ 3\ [en].mkv
SegvAnalysis:
 Segfault happened at: 0x7f6a71f9e97d: mov (%rax),%rdx
 PC (0x7f6a71f9e97d) ok
 source "(%rax)" (0xac3c7e9c) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: totem
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_slice_free1 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstlibav.so
 ?? () from /usr/lib/x86_64-linux-gnu/libavcodec.so.54
Title: totem crashed with SIGSEGV in g_slice_free1()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

Revision history for this message
S. Neumann (karatebomber) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 magazine_chain_pop_head (magazine_chunks=<synthetic pointer>) at /build/buildd/glib2.0-2.39.91/./glib/gslice.c:539
 magazine_chain_prepare_fields (magazine_chunks=0x7f6a241085d0) at /build/buildd/glib2.0-2.39.91/./glib/gslice.c:620
 magazine_cache_push_magazine (ix=42, magazine_chunks=<optimized out>, count=4) at /build/buildd/glib2.0-2.39.91/./glib/gslice.c:691
 thread_memory_magazine2_unload (ix=<optimized out>, tmem=<optimized out>) at /build/buildd/glib2.0-2.39.91/./glib/gslice.c:809
 g_slice_free1 (mem_size=<optimized out>, mem_block=0x7f6a24108b30) at /build/buildd/glib2.0-2.39.91/./glib/gslice.c:1094

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 totem (Ubuntu):
importance: Undecided → Medium
summary: - totem crashed with SIGSEGV in g_slice_free1()
+ totem crashed with SIGSEGV in magazine_chain_pop_head()
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: totem crashed with SIGSEGV in magazine_chain_pop_head()

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

Changed in totem (Ubuntu):
status: New → Confirmed
summary: - totem crashed with SIGSEGV in magazine_chain_pop_head()
+ totem crashed with SIGSEGV in magazine_chain_pop_head() from
+ magazine_chain_prepare_fields() from magazine_cache_push_magazine() from
+ thread_memory_magazine2_unload() from g_slice_free1()
information type: Private → Public
Revision history for this message
Sebastien Bacher (seb128) wrote :

is that still an issue in newer versions?

Changed in totem (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Looks like only trusty is affected. So that's still supported, but only till the end of this month, apparently...

https://wiki.ubuntu.com/Releases

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in totem (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.