diff options
| author | Ruslan Tkhakokhov <rthakohov@google.com> | 2021-08-18 07:22:40 +0100 |
|---|---|---|
| committer | Ruslan Tkhakokhov <rthakohov@google.com> | 2021-11-25 22:24:06 +0000 |
| commit | 4428e22d67e626eaa575098f334d71a60debdf3b (patch) | |
| tree | b8deba68c71b70ad456fda2b1a4764009649209d /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | a656a4e4e4c4bdc807b4bbe6688fe2d4a1530620 (diff) | |
Dispose of TransportClient in BMS#beginRestoreSession
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
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions