Add InputReceiverData to persist AInputReceiver and dependent object In earlier changes we had added logic to create AInputReceiver[1] when root compositor frame sink was created with flag `create_input_receiver` set to true. But the input receiver and related objects were being destroyed immediately. In this change we are: * Introducing InputReceiverData class for managing lifecycle of AInputReceiver and other related objects. * Calling AInputReceiver_release causes crash on Android 15: b/368251173, to work around that instead of destroying input receiver a single instance is being kept around, and re used. * For now we are not handling split window scenarios, since this would mean making multiple input receivers for the windows and keeping them around, since we can't call AInputReceiver_release. Bug: 364201006 Change-Id: Ia8dbc079957c2c2e26bfd912439d0bcc16f23221 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5967973 Reviewed-by: Jonathan Ross <jonross@chromium.org> Reviewed-by: Alexander Timin <altimin@chromium.org> Commit-Queue: Kartar Singh <kartarsingh@google.com> Cr-Commit-Position: refs/heads/main@{#1387434}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.