Ensure we register the input consumer on the ui thread.
- We register the input consumer on the interim choreographer thread but unregister the input consumer on the UI thread when invalidating the previous handler. This may have caused a race condition where the disposal of the input consumer overlapped with the registration of the new one (they share a key in the input consumer map in the system) Bug: 73505150 Test: Unable to reproduce, this is a hypothetical fix Change-Id: I20a9a7be967f5072bbf50ce12e5e61cb939e3c75
Loading
Please register or sign in to comment