Refactor PointerChoreographer lock
Pointer choreographer and WindowInfoListener use separate locks which is problematic. As WindowInfosUpdate callback is triggered from the display thread, a deadlock might occur due to race between display and reader thread. Both trying to acquire both the locks. This becomes much more likely when we have multiple displays connected. Test: Verify pointer indicators are hidden on screenshots of secure windows Test: atest inputflinger_tests Bug: 367660694 Flag: EXEMPT refactor Change-Id: I7417c0071322a093643734432f8f0236bd89a317
Loading
Please register or sign in to comment