summaryrefslogtreecommitdiff
path: root/core/java/android/inputmethodservice/InputMethodService.java
diff options
context:
space:
mode:
authorRuslan Tkhakokhov <rthakohov@google.com>2021-08-18 07:22:40 +0100
committerRuslan Tkhakokhov <rthakohov@google.com>2022-01-04 14:39:09 +0000
commita95214a4d84820db779f7fe8cebc2f38ddb7c561 (patch)
tree4ea56c00e1e7b11c334cbbe022c6848561cceb45 /core/java/android/inputmethodservice/InputMethodService.java
parentc2dc611aca82dddb5a4fdc88ec168d5c3aa868fb (diff)
Dispose of TransportClient in BMS#beginRestoreSession
(This CL was already merged into sc-v2-dev but has to be manually cherry-picked into master due to a conflict.) Currently we create a new transport client in UserBackupManagerService#beginRestoreSession but don't dispose of it properly which leaves us bound to the transport service. The client can eventually be garbage collected triggering the finalize() method which will unbind the transport but there're no guarantees as to whne it will happen. Explicitly dispose of the transport client like it's done in other places in the code. Bug: 196377372 Test: 1. Manual: 1.1. Run restore for any package via 'adb shell bmgr' 1.2. Check logcat for TransportClientManager to make sure the transport client created in beginRestoreSession() has been cleaned up. Change-Id: I9304768330ab796fccf67b544766d87461d977d7 (cherry picked from commit 4428e22d67e626eaa575098f334d71a60debdf3b)
Diffstat (limited to 'core/java/android/inputmethodservice/InputMethodService.java')
0 files changed, 0 insertions, 0 deletions