Always stop dhcp server even it is obsolete
If dhcp server is obsolete, explicitly stop it to shut down its thread. Bug: 161418295 Test: atest CtsTetheringTest Change-Id: Ic5b876bd23711ec8d832879a7baee0495246b218
This commit is contained in:
@@ -422,9 +422,13 @@ public class IpServer extends StateMachine {
|
||||
getHandler().post(() -> {
|
||||
// We are on the handler thread: mDhcpServerStartIndex can be read safely.
|
||||
if (mStartIndex != mDhcpServerStartIndex) {
|
||||
// This start request is obsolete. When the |server| binder token goes out of
|
||||
// scope, the garbage collector will finalize it, which causes the network stack
|
||||
// process garbage collector to collect the server itself.
|
||||
// This start request is obsolete. Explicitly stop the DHCP server to shut
|
||||
// down its thread. When the |server| binder token goes out of scope, the
|
||||
// garbage collector will finalize it, which causes the network stack process
|
||||
// garbage collector to collect the server itself.
|
||||
try {
|
||||
server.stop(null);
|
||||
} catch (RemoteException e) { }
|
||||
return;
|
||||
}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user