[soundnua]: gnome-control-center crashed with SIGABRT in pa_memblock_acquire()

Bug #943531 reported by Афанасьев Антон
40
This bug affects 5 people
Affects Status Importance Assigned to Milestone
pulseaudio (Ubuntu)
Expired
Medium
Unassigned

Bug Description

volume change in volume settings

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.3.90-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
Date: Wed Feb 29 21:09:57 2012
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120108)
ProcCmdline: gnome-control-center sound-nua
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=ru_RU.UTF-8
Signal: 6
SourcePackage: gnome-control-center
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 pa_memblock_acquire () from /usr/lib/x86_64-linux-gnu/libpulsecommon-1.1.so
 pa_stream_peek () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
 ?? () from /usr/lib/control-center-1/panels/libsoundnua.so
Title: [soundnua]: gnome-control-center crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip git gitlab lpadmin plugdev sambashare sudo
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.2-0ubuntu2
 deja-dup 21.90-0ubuntu1
 gnome-bluetooth 3.2.2-0ubuntu2
 indicator-datetime 0.3.90-0ubuntu1

Revision history for this message
Афанасьев Антон (callofbeliar) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 pa_memblock_acquire (b=<optimized out>) at pulsecore/memblock.c:454
 pa_memblock_acquire (b=<optimized out>) at pulsecore/memblock.c:453
 pa_stream_peek (s=0x7fcb20e9bc00, data=0x7fff99373d78, length=0x7fff99373d68) at pulse/stream.c:1600
 on_monitor_read_callback (s=0x7fcb20e9bc00, length=4, userdata=<optimized out>) at gvc-mixer-dialog.c:273
 pstream_memblock_callback (p=<optimized out>, channel=<optimized out>, offset=0, seek=PA_SEEK_RELATIVE, chunk=0x7fff99373e10, userdata=0x7fcb20ad2e80) at pulse/context.c:365

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 gnome-control-center (Ubuntu):
importance: Undecided → Medium
summary: - [soundnua]: gnome-control-center crashed with SIGABRT in raise()
+ [soundnua]: gnome-control-center crashed with SIGABRT in
+ pa_memblock_acquire()
tags: removed: need-amd64-retrace
visibility: private → public
affects: gnome-control-center (Ubuntu) → pulseaudio (Ubuntu)
Revision history for this message
David Henningsson (diwic) wrote :

Hi,
Is this still a problem on Pulseaudio 1.1-0ubuntu12? There was a bug fix released that could possibly have caused this crash as well.

Changed in pulseaudio (Ubuntu):
status: New → Incomplete
Revision history for this message
David Henningsson (diwic) wrote :

This looks tricky. It's related to playing back something that seeks forward four bytes, and that seek then updates the monitor stream. Then the stream tries to read four bytes from something that does not have a memblock, and no silence is allowed to be handed out either.

What pulseaudio clients were you using at this timing for playback and/or recording? Maybe I can reproduce it here somehow.

Revision history for this message
Michael Terry (mterry) wrote :

I was using either banshee or flash on Youtube. Sorry I don't remember which. :-/

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

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

Changed in pulseaudio (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Taras Prokopenko (tpro) wrote :

got this crash when deadbeef was playing and i've changed output sink via audio system settings

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

This bug has been closed for 6 years :)

If you have any ongoing issue then please open a new bug.

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.