From: Piotr Kosko/Tizen API (PLT) /SRPOL/Engineer/Samsung Electronics <p.kosko@samsung.com>
Date: Tue, 15 Oct 2024 12:15:33 +0000 (+0200)
Subject: [HAM] Fixed deadlock issue
X-Git-Tag: accepted/tizen/unified/20241016.160059^0
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=refs%2Fchanges%2F26%2F319126%2F1;p=platform%2Fcore%2Fapi%2Fwebapi-plugins.git

[HAM] Fixed deadlock issue

Issue was visible in manual HAM test on emulator:
- HumanActivityMonitorManager_readRecorderData_type_PRESSURE

addRecordedData is called via SensorRecordedDataCb which is called in
ReadRecorderDataImpl function which has mutex locked there. Because of
that there was a deadlock.

Change-Id: I0ef35bb9674b50e9314e037fcf0ceb6feb82e084
---

diff --git a/src/humanactivitymonitor/humanactivitymonitor_manager.cc b/src/humanactivitymonitor/humanactivitymonitor_manager.cc
index 67031e39..3e54beec 100644
--- a/src/humanactivitymonitor/humanactivitymonitor_manager.cc
+++ b/src/humanactivitymonitor/humanactivitymonitor_manager.cc
@@ -661,7 +661,6 @@ class HumanActivityMonitorManager::Monitor::SensorMonitor
 
   void addRecordedData(picojson::value* data) {
     ScopeLogger();
-    std::lock_guard<std::mutex> lock(mutex_);
     recorded_data_->push_back(*data);
   }