unity8 crashed with SIGSEGV

[Chris Wayne]

When launching a scope, unity8 crashes

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: unity8 7.90+14.10.20140725-0ubuntu1
Uname: Linux 3.4.0-1-hammerhead armv7l
ApportVersion: 2.14.4-0ubuntu2
Architecture: armhf
CurrentDesktop: Unity
Date: Fri Jul 25 11:34:08 2014
ExecutablePath: /usr/bin/unity8
InstallationDate: Installed on 2014-07-25 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140725-020205)
ProcCmdline: unity8
Signal: 11
SourcePackage: unity8
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/arm-linux-gnueabihf/libunity-scopes.so.2
 ?? () from /usr/lib/arm-linux-gnueabihf/libunity-scopes.so.2
 ?? () from /usr/lib/arm-linux-gnueabihf/libunity-scopes.so.2
 ?? () from /usr/lib/arm-linux-gnueabihf/libunity-scopes.so.2
Title: unity8 crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dialout dip nopasswdlogin plugdev sudo tty video

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 unity::scopes::internal::ReplyObject::finished (this=0x2169c58, r=unity::scopes::ListenerBase::Error, error_message=...) at /build/buildd/unity-scopes-api-0.5.2+14.10.20140723/src/scopes/internal/ReplyObject.cpp:160
 operator() (__closure=0x1bccbe0) at /build/buildd/unity-scopes-api-0.5.2+14.10.20140723/src/scopes/internal/ReplyObject.cpp:54
 std::_Function_handler<void(), unity::scopes::internal::ReplyObject::ReplyObject(const SPtr&, const unity::scopes::internal::RuntimeImpl*, const string&)::<lambda()> >::_M_invoke(const std::_Any_data &) (__functor=...) at /usr/include/c++/4.9/functional:2039
 unity::scopes::internal::Reaper::remove_zombies (this=<optimized out>, zombies=...) at /build/buildd/unity-scopes-api-0.5.2+14.10.20140723/src/scopes/internal/Reaper.cpp:300

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Chris Wayne (cwayne)]

The steps to reproduce were basically going to the scopes scope, then opening/closing scopes very quickly, so this was more of a stress test than anything

[Chris Gagnon (chris.gagnon)]

It looks like this is the issue on errors.ubuntu.com https://errors.ubuntu.com/oops/f19d2262-1415-11e4-8013-fa163e4aaad4

[Michi Henning (michihenning)]

Thanks for the bug report. Mea culpa. I was calling disconnect() before calling finished() on the ListenerBase. Normally, this isn't a problem because the middleware holds the reference count of the servant high while an operation is in progress. But, in this case, the call was triggered by the reaper (while no operation was in progress), so the call into ListenerBase::finished() went into an already-destroyed instance.

[PS Jenkins bot (ps-jenkins)]

Fix committed into lp:unity-scopes-api/devel at revision None, scheduled for release in unity-scopes-api, milestone Unknown