bluetoothd crashed with SIGSEGV in malloc_consolidate()

Bug #1695079 reported by Matthias Andree
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
New
Medium
Unassigned

Bug Description

found this pending crash report after login

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: bluez 5.37-0ubuntu5
ProcVersionSignature: Ubuntu 4.10.0-22.24~16.04.1-lowlatency 4.10.15
Uname: Linux 4.10.0-22-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Thu Jun 1 21:16:46 2017
ExecutablePath: /usr/lib/bluetooth/bluetoothd
ExecutableTimestamp: 1456846426
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: System manufacturer System Product Name
ProcCmdline: /usr/lib/bluetooth/bluetoothd
ProcCwd: /
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-22-lowlatency root=/dev/mapper/vgcrypt0-root ro ip=192.168.33.4::192.168.33.253 quiet nvidia_drm.modeset=1 crashkernel=384M-:128M irqpoll
RetraceOutdatedPackages: no debug symbol package found for liblzma5
Signal: 11
SourcePackage: bluez
StacktraceTop:
 malloc_consolidate (av=av@entry=0x7f558b1c6b20 <main_arena>) at malloc.c:4167
 _int_malloc (av=av@entry=0x7f558b1c6b20 <main_arena>, bytes=bytes@entry=8192) at malloc.c:3448
 __libc_calloc (n=<optimized out>, elem_size=<optimized out>) at malloc.c:3234
 __GI___open_memstream (bufloc=bufloc@entry=0x7ffc798b0bb0, sizeloc=sizeloc@entry=0x7ffc798b0bb8) at memstream.c:83
 __GI___vsyslog_chk (pri=30, pri@entry=6, flag=flag@entry=1, fmt=fmt@entry=0x5560910fd518 "Endpoint unregistered: sender=%s path=%s", ap=ap@entry=0x7ffc798b0c80) at ../misc/syslog.c:167
Title: bluetoothd crashed with SIGSEGV in malloc_consolidate()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 04/13/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3503
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A78T-E
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/13/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78T-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
hciconfig:
 hci0: Type: BR/EDR Bus: USB
  BD Address: 00:19:15:4E:47:D7 ACL MTU: 1017:8 SCO MTU: 64:0
  UP RUNNING PSCAN
  RX bytes:3488668 acl:62 sco:68335 events:93 errors:0
  TX bytes:1625 acl:56 sco:0 commands:59 errors:0
rfkill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

Revision history for this message
Matthias Andree (matthias-andree) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 malloc_consolidate (av=av@entry=0x7f558b1c6b20 <main_arena>) at malloc.c:4167
 _int_malloc (av=av@entry=0x7f558b1c6b20 <main_arena>, bytes=bytes@entry=8192) at malloc.c:3448
 __libc_calloc (n=<optimized out>, elem_size=<optimized out>) at malloc.c:3234
 __GI___open_memstream (bufloc=bufloc@entry=0x7ffc798b0bb0, sizeloc=sizeloc@entry=0x7ffc798b0bb8) at memstream.c:83
 __GI___vsyslog_chk (pri=30, pri@entry=6, flag=flag@entry=1, fmt=fmt@entry=0x5560910fd518 "Endpoint unregistered: sender=%s path=%s", ap=ap@entry=0x7ffc798b0c80) at ../misc/syslog.c:167

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 bluez (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1690013, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

information type: Private → Public
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.