compiz crashed with SIGSEGV in PlacesResultsController::Clear()

[Nicolas Riesco]

Binary package hint: unity

Unity froze and re-started after pressing ALT+F2 and typing a few letters.

Unity has frozen twice today, forcing me to go to a terminal (CTRL+ALT+F1) and reboot (sudo reboot).

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: unity 3.8.8-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
Date: Sun Apr 17 15:18:22 2011
ExecutablePath: /usr/bin/compiz
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f396effb924 <_ZN23PlacesResultsController5ClearEv+36>: mov (%rdi),%rax
 PC (0x7f396effb924) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 PlacesResultsController::Clear() () from /usr/lib/compiz/libunityshell.so
 PlacesView::SetActiveEntry(PlaceEntry*, unsigned int, char const*, bool) () from /usr/lib/compiz/libunityshell.so
 PlacesController::OnViewShowHideFrame(PlacesController*) () from /usr/lib/compiz/libunityshell.so
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: compiz crashed with SIGSEGV in PlacesResultsController::Clear()
UpgradeStatus: Upgraded to natty on 2011-04-04 (12 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse libvirtd lpadmin mail netdev plugdev powerdev scanner tape users uucp video

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #761211, 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.