compiz crashed with SIGSEGV in malloc()

[Max Bowsher]

Crashed after unticking "Window Switcher" and ticking "Static Window Switcher" in ccsm

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity 4.22.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Thu Oct 6 14:43:09 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f2ceeeedd1d: cmp 0x18(%rdx),%r12
 PC (0x7f2ceeeedd1d) ok
 source "0x18(%rdx)" (0x2a000060002261c) not located in a known VMA region (needed readable region)!
 destination "%r12" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 malloc () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 g_dir_open (path=0x1611390 "/usr/share/thumbnailers", flags=<optimized out>, error=0x0) at /build/buildd/glib2.0-2.30.0/./glib/gdir.c:124
Title: compiz crashed with SIGSEGV in malloc()
UpgradeStatus: Upgraded to oneiric on 2011-10-06 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare sbuild

[Apport retracing service (apport)]

StacktraceTop:
 malloc_consolidate (av=0x7f2cef20f1c0) at malloc.c:5169
 malloc_consolidate (av=0x7f2cef20f1c0) at malloc.c:5115
 _int_malloc (av=0x7f2cef20f1c0, bytes=32808) at malloc.c:4373
 __GI___libc_malloc (bytes=32808) at malloc.c:3660
 __alloc_dir (fd=18, close_fd=true, statp=0x0) at ../sysdeps/unix/opendir.c:186

[Tim Penhey (thumper)]

Hi Max,

Does this still occur for you? We have made quite a few changes in that area.

Tim

[Max Bowsher (maxb)]

I think it is still a problem. I was definitely able, on current oneiric, to cause unity to exit by switching the settings in ccsm as described before.

Unfortunately the upgrade to release version had turned off apport, so no crash was captured.

I'll try to retrigger it.

[Max Bowsher (maxb)]

I've filed bug 886017 (slightly different trigger conditions) and bug 886019 (exactly the same triggering conditions) to get fresh retraces against current oneiric.

[Omer Akram (om26er)]

are there any steps to reproduce this specific crash?

[Launchpad Janitor (janitor)]

[Expired for unity because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

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