compiz assert failure: *** glibc detected *** compiz: free(): invalid pointer: 0x00007f516ea0fe84 ***

Bug #1045965 reported by Brian Murray
80
This bug affects 10 people
Affects Status Importance Assigned to Milestone
Compiz
Expired
Undecided
Unassigned
compiz (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

This happens immediately after trying to login and after every log in attempt.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: compiz-core 1:0.9.8.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
Uname: Linux 3.5.0-13-generic x86_64
ApportVersion: 2.5.1-0ubuntu4
Architecture: amd64
AssertionMessage: *** glibc detected *** compiz: free(): invalid pointer: 0x00007f516ea0fe84 ***
CheckboxSubmission: fee5e196cb921cbd36888f428b38b488
CheckboxSystem: 2a6f54df59af338184485e85cbcf0d32
CrashCounter: 1
Date: Tue Sep 4 10:38:27 2012
DistUpgraded: 2012-08-28 20:17:13,654 DEBUG enabling apt cron job
DistroCodename: quantal
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
ExecutableTimestamp: 1346448992
GraphicsCard:
 Advanced Micro Devices [AMD] nee ATI RV730 PRO [Radeon HD 4650] [1002:9498] (prog-if 00 [VGA controller])
   Subsystem: XFX Pine Group Inc. Device [1682:2451]
MachineType: Dell Inc. Dell DXP051
PlymouthDebug: Error: [Errno 13] Permission denied: '/var/log/plymouth-debug.log'
ProcCmdline: compiz --sm-client-id 10a57e582822016516133107316874715500000028130066
ProcCwd: /home/theman
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-13-generic root=UUID=615bf598-a228-4bcc-9e4c-2aceb30c7c3e ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: compiz
StacktraceTop:
 __libc_message (do_abort=2, fmt=0x7f517352dfd0 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:201
 malloc_printerr (action=3, str=0x7f517352af81 "free(): invalid pointer", ptr=<optimized out>) at malloc.c:5007
 language_names_cache_free (data=0x7f5138005960) at /build/buildd/glib2.0-2.33.10/./glib/gcharset.c:528
 __nptl_deallocate_tsd () at pthread_create.c:156
 start_thread (arg=0x7f514d9e9700) at pthread_create.c:315
Title: compiz assert failure: *** glibc detected *** compiz: free(): invalid pointer: 0x00007f516ea0fe84 ***
UpgradeStatus: Upgraded to quantal on 2012-08-29 (6 days ago)
UserGroups: adm admin audio cdrom dialout dip family floppy fuse libvirtd lpadmin plugdev pulse pulse-access sambashare sbuild scanner video
dmi.bios.date: 10/28/2005
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A02
dmi.board.name: 0YC523
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA02:bd10/28/2005:svnDellInc.:pnDellDXP051:pvr:rvnDellInc.:rn0YC523:rvr:cvnDellInc.:ct7:cvr:
dmi.product.name: Dell DXP051
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.8.0-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.38-0ubuntu2
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120821.c1114c61-0ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 9.0~git20120821.c1114c61-0ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120821.c1114c61-0ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.3-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-4~ubuntu1

Revision history for this message
Brian Murray (brian-murray) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #750386, so 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. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-amd64-retrace
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
Revision history for this message
Tim Penhey (thumper) wrote :

Slightly frustrated there is no stacktrace, I get this every time logging in.

Interestingly though, if I switch to a vt and start unity manually, all is fine.

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

A stack trace would not help in the free() because it's a delayed effect from earlier heap corruption.

All - Please try this to produce a better crash report that will help us find the root cause of the problem:

    env MALLOC_CHECK_=3 G_SLICE=always-malloc unity --replace

Changed in compiz:
status: New → Incomplete
Changed in compiz (Ubuntu):
status: Confirmed → Incomplete
tags: added: compiz-0.9
Revision history for this message
mdmcginn (mcweb) wrote :

I can certainly generate crashes when I run env MALLOC_CHECK_=3 G_SLICE=always-malloc unity --replace. What do I do after that? It's not giving me anything new in /var/crash. I tried ubuntu-bug and ended up with https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1061467. When I try ubuntu-bug _usr_bin_compiz.1000.crash, to report an earlier crash, it eventually tells me to check my internet connection. The file size is 312894645.

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

I ran into the same problem. I'm not sure why it then fails to report a crash :(

Revision history for this message
Marius B. Kotsbak (mariusko) wrote :

What about running it in gdb?:

MALLOC_CHECK_=3 G_SLICE=always-malloc gdb --args "replace" /usr/bin/unity

and then when it crashes, type "backtrace" and then paste here what appears.

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

That certainly works but I was aiming for something more user-friendly to ask regular people to do...

Revision history for this message
mdmcginn (mcweb) wrote :

michael@doulos:~/Desktop$ MALLOC_CHECK_=3 G_SLICE=always-malloc gdb --args "replace" /usr/bin/unity
GNU gdb (GDB) 7.5-ubuntu
<snip copyright info>
Reading symbols from /usr/bin/replace...(no debugging symbols found)...done.
(gdb) backtrace
No stack.
(gdb)

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

See? Normal people don't understand gdb so we shouldn't normally ask them to without detailed instructions :)

Try this:

ulimit -c unlimited
env MALLOC_CHECK_=3 G_SLICE=always-malloc gdb --args "replace" /usr/bin/unity
# Wait for the crash
gdb /usr/bin/compiz core
(gdb) bt
# Now copy the output

Revision history for this message
Marius B. Kotsbak (mariusko) wrote :

Sorry. You need to type "run" after gdb has started.

Revision history for this message
mdmcginn (mcweb) wrote :

It's a little difficult to run all those commands before it crashes, and also difficult to run commands afterwards if the screen is frozen. I tried putting them into a script. Would a script be a better solution for normal people? Still no output, though.

Revision history for this message
Marius B. Kotsbak (mariusko) wrote :

Unity is a python script, so it won't work, but it supports debugging:

--debug Run unity under gdb and print a backtrace on crash. /!\
                    Only if devs ask for it.

i.e. run "unity --debug --replace" before the crash (preferrable in a console terminal (hit CTRL-ALT-F1 and log in, then CTRL-ALT-F7)).

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

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

Changed in compiz:
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

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