compiz crashed with SIGSEGV in g_main_context_dispatch()

[Frank Bicknell]

sorry - I was minding my own business and everythign went south. Have been having lots of issues with compiz sucking up all the system memory lately. I did a unity --replace earlier today to fix that latest instance. I can tell you that compiz was taking up only about 5% of memory when it crashed (I run a cron job every 2 minutes to sample the amount of memory compiz is sapping at any time and I have a history file of this). This appears to be related to something other than the memory leak issue?

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity 5.20.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-58.88-generic 3.2.53
Uname: Linux 3.2.0-58-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
CheckboxSubmission: 48349af06a737bc39f5bd5104a6aec3f
CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b
Date: Mon Feb 10 16:35:11 2014
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
MarkForUpload: True
ProcCmdline: compiz --replace
SegvAnalysis:
 Segfault happened at: 0x7f01c60d8abe: mov 0x8(%rsi),%rax
 PC (0x7f01c60d8abe) ok
 source "0x8(%rsi)" (0x474c040abeef020a) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 ?? () from /usr/lib/compiz/libunityshell.so
 ?? () from /usr/lib/compiz/libunityshell.so
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: compiz crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo vboxusers

[Apport retracing service (apport)]

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 #962581, 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.