unity-system-compositor crashed with SIGSEGV in __gxx_personality_v0()

[[e-mail]]

NA

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: unity-system-compositor 0.4.2+16.04.20160219.1-0ubuntu1
Uname: Linux 4.5.0-040500rc7-lowlatency x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia wl
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Fri Mar 18 23:13:49 2016
ExecutablePath: /usr/sbin/unity-system-compositor
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:178d]
   Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d]
InstallationDate: Installed on 2016-02-14 (33 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160214)
ProcCmdline: /usr/sbin/unity-system-compositor --disable-inactivity-policy=true --on-fatal-error-abort --file /run/lightdm-mir-0 --from-dm-fd 12 --to-dm-fd 21 --vt 8
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7f663ec32c3b: mov (%rsi),%rax
 PC (0x7f663ec32c3b) ok
 source "(%rsi)" (0x7f663ad81490) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity-system-compositor
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 __gxx_personality_v0 () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 _Unwind_RaiseException () from /lib/x86_64-linux-gnu/libgcc_s.so.1
 _Unwind_Resume_or_Rethrow () from /lib/x86_64-linux-gnu/libgcc_s.so.1
 __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
Title: unity-system-compositor crashed with SIGSEGV in __gxx_personality_v0()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

version.libdrm: libdrm2 2.4.67-1
version.lightdm: lightdm 1.17.6-0ubuntu1
version.mesa: libegl1-mesa-dev N/A

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