From d95102443e9b7e8e67d3c20294bf1ced47ec1ddd Mon Sep 17 00:00:00 2001 From: "Piotr Kosko/Tizen API (PLT) /SRPOL/Engineer/Samsung Electronics" Date: Tue, 15 Oct 2024 14:15:33 +0200 Subject: [PATCH] [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 --- src/humanactivitymonitor/humanactivitymonitor_manager.cc | 1 - 1 file changed, 1 deletion(-) 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 lock(mutex_); recorded_data_->push_back(*data); } -- 2.34.1