compiz crashed with SIGSEGV in g_object_unref() after raring to saucy upgrade

[Para Siva]

This crash occurred at the first login attempt after raring-> saucy desktop upgrade with amd64 on dell Inspiron.

Steps:
1. Install raring desktop amd64
2. Run dist-upgrade and reboot
3. Run update-manager -d and perform the upgrade
4. Reboot and login
5. The crash occurred at this point

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3
Uname: Linux 3.9.0-2-generic x86_64
ApportVersion: 2.10.1-0ubuntu1
Architecture: amd64
Date: Wed May 22 10:16:58 2013
ExecutablePath: /usr/bin/compiz
ExecutableTimestamp: 1366264808
InstallationDate: Installed on 2013-05-22 (0 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcCmdline: compiz
ProcCwd: /home/ubuntu
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f3dad6eae04 <g_object_unref+20>: cmpq $0x50,(%rax)
 PC (0x7f3dad6eae04) ok
 source "$0x50" ok
 destination "(%rax)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 unity::bamf::Application::~Application() () from /usr/lib/compiz/libunityshell.so
 unity::bamf::Application::~Application() () from /usr/lib/compiz/libunityshell.so
 std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() () from /usr/lib/compiz/libunityshell.so
 unity::launcher::ApplicationLauncherIcon::~ApplicationLauncherIcon() () from /usr/lib/compiz/libunityshell.so
Title: compiz crashed with SIGSEGV in g_object_unref()
UpgradeStatus: Upgraded to saucy on 2013-05-22 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[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 #1181717, 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.