compiz crashed with SIGSEGV in malloc_consolidate()

Bug #1542967 reported by Rocko
42
This bug affects 7 people
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

This crash just happened after the latest updates installed from the main Ubuntu repos as of 2016-02-08 01:30 GMT when trying to login to a desktop.

Because compiz crashes before establishing a usable desktop, I have had to revert back to a snapshot from 2016-02-05 to report the bug. So I don't know if apport is reporting the correct versions of installed packages.

I saw a similar thing happen a couple of weeks ago, and it turned out to be due to an nvidia 352 driver update from xorg-edgers; I purged the package and went back to using the nvidia 352 driver from the main repositories. This fixed the problem at the time - I was able to install all updates and compiz kept working. Note that I'm only using the nvidia driver so bumblebee can turn off the nvidia card.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: compiz-core 1:0.9.12.2+16.04.20151211-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CrashCounter: 1
CurrentDesktop: Unity
Date: Mon Feb 8 10:36:21 2016
DistUpgraded: 2016-01-06 09:07:31,911 DEBUG enabling apt cron job
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-2-generic, x86_64: installed
 bbswitch, 0.8, 4.4.1-040401-generic, x86_64: installed
 nvidia-352-updates, 352.63, 4.4.1-040401-generic, x86_64: installed
 vboxhost, 5.0.14, 4.4.0-2-generic, x86_64: installed
 vboxhost, 5.0.14, 4.4.1-040401-generic, x86_64: installed
ExecutablePath: /usr/bin/compiz
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:050e]
 NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:050e]
InstallationDate: Installed on 2014-11-26 (439 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: Dell Inc. Dell System XPS L502X
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, no user)
 SHELL=/bin/bash
 LANG=en_AU.UTF-8
 LANGUAGE=en_AU:en
 XDG_RUNTIME_DIR=<set>
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-2-generic root=UUID=8d6a5286-c675-44a2-9ee6-581a539e9915 ro rootflags=subvol=@ quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f6075a8e12b <malloc_consolidate+299>: mov 0x8(%r12),%r13
 PC (0x7f6075a8e12b) ok
 source "0x8(%r12)" (0x7f607820c800) not located in a known VMA region (needed readable region)!
 destination "%r13" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 malloc_consolidate (av=av@entry=0x7f6075dd3c00 <main_arena>) at malloc.c:4136
 _int_free (av=0x7f6075dd3c00 <main_arena>, p=<optimised out>, have_lock=0) at malloc.c:4042
 __GI___libc_free (mem=<optimised out>) at malloc.c:2950
 ?? ()
 ?? ()
Title: compiz crashed with SIGSEGV in malloc_consolidate()
UpgradeStatus: Upgraded to xenial on 2016-01-06 (33 days ago)
UserGroups: adm lpadmin sambashare sudo
dmi.bios.date: 05/29/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0NJT03
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnDellInc.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: Dell System XPS L502X
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.66-2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160127-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Mon Feb 8 10:42:34 2016
xserver.configfile: default
xserver.errors: systemd-logind: failed to get session: PID 1831 does not belong to any known session
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 6125
 vendor AUO
xserver.version: 2:1.17.3-2ubuntu2

Revision history for this message
Rocko (rockorequin) wrote :
information type: Private → Public
Revision history for this message
Rocko (rockorequin) wrote :

And once again, the culprit is the nvidia driver. I have all updates installed as of 2015-08-02 06:20 GMT installed EXCEPT the nvidia-352-updates 352.63-0ubuntu3 installed, and the desktop boots OK. If I install 352.63-0ubuntu3, compiz crashes.

Revision history for this message
Rocko (rockorequin) wrote :

FYI, the upgrade log for the nvidia driver says that the only change was that it "added EGL alternatives" (https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-352-updates/352.63-0ubuntu3.)

So just to restate the problem: compiz running the intel driver crashes if nvidia-352-updates 352.63-0ubuntu3 is installed, but doesn't crash the previous version, 352.63-0ubuntu2, is installed, and the only difference is "added EGL alternatives".

Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 malloc_consolidate (av=av@entry=0x7f6075dd3c00 <main_arena>) at malloc.c:4136
 _int_free (av=0x7f6075dd3c00 <main_arena>, p=<optimized out>, have_lock=0) at malloc.c:4042
 __GI___libc_free (mem=<optimized out>) at malloc.c:2950
 ?? () from /tmp/apport_sandbox_y7vJAN/usr/lib/nvidia-352/libGL.so.1
 ?? () from /tmp/apport_sandbox_y7vJAN/usr/lib/nvidia-352/libnvidia-glcore.so.352.63

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 compiz (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Erich E. Hoover (ehoover) wrote :

I am running into the same problem with the nVidia Vulkan driver (https://launchpad.net/~canonical-x/+archive/ubuntu/vulkan). At first I thought it was that I updated to 355.00.29, but downgrading to 355.00.26 and it did not fix the issue. This problem was not happening the other day, but something in the large list of updates I installed this morning must have caused the problem. The problem does not exist if I switch to the 361 driver, but I'm in the middle of building a Vulkan wrapper for Wine...

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

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

Changed in compiz (Ubuntu):
status: New → Confirmed
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.