pulseaudio crashed with SIGSEGV in dbus_message_lock()

[Heilner Garcia]

using jack

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: pulseaudio 1:0.99.3-0ubuntu5
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd4600000 irq 44'
   Mixer name : 'Realtek ALC272'
   Components : 'HDA:10ec0272,1179ff10,00100001 HDA:11c11040,11790001,00100200'
   Controls : 20
   Simple ctrls : 12
Card1.Amixer.info:
 Card hw:1 'Device'/'C-Media Electronics Inc. USB Multimedia Audio Device at usb-0000:00:1d.7-2.2, f'
   Mixer name : 'USB Mixer'
   Components : 'USB0d8c:0105'
   Controls : 9
   Simple ctrls : 6
Date: Sun Sep 18 17:45:09 2011
ExecutablePath: /usr/bin/pulseaudio
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
ProcEnviron:
 LANGUAGE=es_VE:es
 PATH=(custom, no user)
 LANG=es_VE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f34324e1da3: mov %ebx,(%rax)
 PC (0x7f34324e1da3) ok
 source "%ebx" ok
 destination "(%rax)" (0x00000004) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: pulseaudio
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 dbus_message_lock () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
Title: pulseaudio crashed with SIGSEGV in dbus_message_lock()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 12/15/2009
dmi.bios.vendor: INSYDE
dmi.bios.version: 1.50
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDE:bvr1.50:bd12/15/2009:svnTOSHIBA:pnSatelliteL505:pvrPSLL0U-01P00D:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Satellite L505
dmi.product.version: PSLL0U-01P00D
dmi.sys.vendor: TOSHIBA

[Apport retracing service (apport)]

StacktraceTop:
 pack_4_octets (data=0x4 <Address 0x4 out of bounds>, byte_order=0, value=<optimized out>) at ../../dbus/dbus-marshal-basic.c:70
 set_4_octets (str=<optimized out>, offset=<optimized out>, value=<optimized out>, byte_order=0) at ../../dbus/dbus-marshal-basic.c:236
 dbus_message_lock (message=0x1b2a5a0) at ../../dbus/dbus-message.c:333
 do_writing (transport=<optimized out>) at ../../dbus/dbus-transport-socket.c:541
 do_writing (transport=0x1ac8200) at ../../dbus/dbus-transport-socket.c:494

[David Henningsson (diwic)]

Hmm, this is bothering me (failing thread):

#11 0x00007f34324c4b54 in dbus_bus_register (connection=0x7f341800acb0, error=0x7f341e8e1e10) at ../../dbus/dbus-bus.c:698
        message = 0x1b2d5d0
        reply = <optimized out>
        name = <optimized out>
        bd = 0x7f3418008640
        retval = 0
        __FUNCTION__ = "dbus_bus_register"

Another thread:

#6 0x00007f34324c4b54 in dbus_bus_register (connection=0x1b410e0, error=0x7f341f0e2dd0) at ../../dbus/dbus-bus.c:698
        message = 0x1b1d670
        reply = <optimized out>
        name = <optimized out>
        bd = 0x191e100
        retval = 0
        __FUNCTION__ = "dbus_bus_register"

Apart from the bd pointer being very different on these threads, two threads shouldn't be at ../../dbus/dbus-bus.c:698 at the same time, because that line is protected by a mutex calles "bus_data".
Reassigning to dbus for further analysis.

[Launchpad Janitor (janitor)]

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