Delete mController when eventHub device is going away
When an event hub device is going away, the controller associated with it should be deleted. Before this CL, mController would remain, and its use would result in an illegal memory access, because it was storing a reference to a deleted context. Bug: 245770596 Test: atest inputflinger_tests:InputDeviceTest#DumpDoesNotCrash Merged-In: I298f43172472f74fa4d5d8e0b7f52bd5c13d14f7 Change-Id: I298f43172472f74fa4d5d8e0b7f52bd5c13d14f7 (cherry picked from commit 30feb8c1)
Showing
- services/inputflinger/reader/InputDevice.cpp 4 additions, 0 deletionsservices/inputflinger/reader/InputDevice.cpp
- services/inputflinger/reader/controller/PeripheralController.cpp 4 additions, 0 deletions...s/inputflinger/reader/controller/PeripheralController.cpp
- services/inputflinger/reader/controller/PeripheralController.h 2 additions, 0 deletions...ces/inputflinger/reader/controller/PeripheralController.h
- services/inputflinger/reader/controller/PeripheralControllerInterface.h 2 additions, 0 deletions...flinger/reader/controller/PeripheralControllerInterface.h
- services/inputflinger/tests/InputReader_test.cpp 18 additions, 0 deletionsservices/inputflinger/tests/InputReader_test.cpp
Loading
Please register or sign in to comment