diff options
| author | Anthony Stange <stange@google.com> | 2020-08-11 12:46:31 -0400 |
|---|---|---|
| committer | Anthony Stange <stange@google.com> | 2020-08-11 21:43:09 +0000 |
| commit | 55a4f59fb8ca7fb83b3ca14d560c30e2c5239a16 (patch) | |
| tree | 6e73a82f5afe259a5e2c217df1c7c61b8ee70c35 /identity/support/src/cppbor_parse.cpp | |
| parent | d8f664a3bdd99f5370e3e535c0a7a8fdf9d4707f (diff) | |
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
Diffstat (limited to 'identity/support/src/cppbor_parse.cpp')
0 files changed, 0 insertions, 0 deletions