Anthony Stange 55a4f59fb8 Fix double release of ScopedWakelock
Today, when a ScopedWakelock is moved, the default move constructor
doesn't unlock the old wakelock instance. This results in the moved
ScopedWakelock instance decrementing the wakelock ref count which leaves
the multi-HAL out of sync from the sensor service.

Fix this by adding a custom move constructor / operator to ensure old
state is cleared on the moved instance.

Bug: 163468874
Test: Load multi-HAL and verify that it properly waits to release the
wakelock until the sensor service notifies that it has a lock held.
Test: Run unit tests

Change-Id: Ifd5a3c7596f78d7a756c4472f30efb625d670791
2020-08-11 21:43:09 +00:00
2020-04-07 16:37:40 -07:00
2020-04-07 16:37:40 -07:00
2020-06-22 06:48:29 +00:00
2020-04-07 16:37:40 -07:00
2020-04-07 16:37:40 -07:00
2020-04-07 16:37:40 -07:00
2020-04-07 16:37:40 -07:00
2020-04-07 16:37:40 -07:00
2020-05-13 17:20:03 +00:00
2020-04-07 16:37:40 -07:00
2020-04-07 16:37:40 -07:00
2020-04-09 08:27:34 +00:00
2020-04-07 16:37:40 -07:00
2020-04-07 16:37:40 -07:00
2020-04-07 16:37:40 -07:00
2019-04-23 12:51:21 -07:00
2020-07-08 17:56:49 +00:00
2020-04-07 16:37:40 -07:00
2020-04-07 16:37:40 -07:00
2020-04-07 16:37:40 -07:00
2020-04-09 08:27:34 +00:00
2020-04-07 16:37:40 -07:00
2020-04-07 16:37:40 -07:00
2019-12-13 14:24:23 -08:00
2016-08-30 11:28:36 -07:00
2016-08-30 11:28:36 -07:00
2019-12-10 09:51:58 -08:00
Description
No description provided
134 MiB
Languages
C++ 56.3%
AIDL 41.2%
C 1.5%
Rust 0.4%
Java 0.4%
Other 0.1%