tree c7fde2b55f1b788d615e522d948d64c9e158ae01
parent f2ad76b32cea5170a5a9a631f49935ae3dd4626d
author James Feist <james.feist@linux.intel.com> 1573166578 -0800
committer James Feist <james.feist@linux.intel.com> 1573168876 +0000

Fix Entity-Manager Crash issue

When using multiple dbus-probe types, we were seeing:

Program received signal SIGBUS, Bus error.
0x00475c6c in std::__shared_count<(__gnu_cxx::_Lock_policy)2>::~__shared_count() ()
(gdb) bt
#0  0x00475c6c in std::__shared_count<(__gnu_cxx::_Lock_policy)2>::~__shared_count() ()
#1  0x00477820 in std::vector<std::shared_ptr<PerformProbe>, std::allocator<std::shared_ptr<PerformProbe> > >::clear() ()
#2  0x0046d594 in ?? ()
#3  0x0046e14c in ?? ()
#4  0x76f60bd0 in ?? () from /lib/libsystemd.so.0
Backtrace stopped: previous frame identical to this frame (corrupt stack?)


The logic in this was quite bad, by moving the storage of
PerformProbe shared_ptrs into the captures, we don't need
to worry about calling clear ever, so we won't run into this
problem. This was reordered to fix the issue.

Tested: On system that frequently saw the crash, it went
away, all sensors still available.

Change-Id: Icacb8861466816df64b24efe940e5a732102345a
Signed-off-by: James Feist <james.feist@linux.intel.com>