Canceled gesture navigation does not produce ACTION_CANCEL [401872146]

Assigned

Bug

NeedsInfo

Status Update

No update yet.

Description

ha...@gmail.com

created issue #1

Mar 9, 2025 09:39PM

Running Android 15 on Pixel 9 Pro. I have discovered what I consider a critical flaw in the touch event system. Any game/app that keeps track of ACTION_DOWN and ACTION_UP/ACTION_CANCEL can easily break when performing the gesture below. For instance, in our game engine, we have a bug where the game gets stuck in "mouse pressed" state. Very unfortunate for the player :P

DOWN followed by nothing? This simply cannot be right!

Steps to reproduce

Create a new "Empty Views Activity" in Android Studio. Choose Java.
Override onTouchEvent as shown below.
Start navigation gesture from the right side.
When the "navigate" arrow appears, swipe back to the right side. The arrow disappears.
Release your finger.

@Override
public boolean onTouchEvent(MotionEvent event) {
    String s = MotionEvent.actionToString((event.getAction()));
    Log.d("TOUCH", s);

    return super.onTouchEvent(event);
}

Expected output

ACTION_DOWN
ACTION_CANCEL

Actual output

ACTION_DOWN

ACTION_DOWN
ACTION_MOVE

Attaching an image of the "navigate" arrow.

navigation-arrow.png

9.8 KB

View

Download

Comments

vi...@google.com <vi...@google.com> #2Mar 10, 2025 03:59AM

Assigned to vi...@google.com.

I believe https://chromium-review.googlesource.com/c/chromiumos/overlays/chromiumos-overlay/+/5346490 should make this work, though I also noticed that we're not passing any form of --jobs to x.py, so RBE's "more parallelism" benefit doesn't really exist as it stands.

On the other hand, passing --jobs=$(get_makeopts_jobs) applies that limit to both Rust's and LLVM's builds. cargo -j1000 isn't being a good citizen on machines that are also running make -j$(ncpu).

Maybe there's room for a local patch, and/or advocating upstream for --llvm-jobs, depending on whether reclient can be made to work with the rustc invocations here.

ha...@gmail.com <ha...@gmail.com> #3Mar 10, 2025 06:49AM

Hrmm,

FAILED: lib/Demangle/CMakeFiles/LLVMDemangle.dir/MicrosoftDemangle.cpp.o 
/var/tmp/portage/dev-lang/rust-host-1.75.0-r1/files/reclient_compiler_launcher.sh /usr/bin/x86_64-pc-linux-gnu-clang++ -DGTEST_HAS_RTTI=0 -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/var/tmp/portage/dev-lang/rust-host-1.75.0-r1/work/build/x86_64-pc-linux-gnu/llvm/build/lib/Demangle -I/var/tmp/portage/dev-lang/rust-host-1.75.0-r1/work/rustc-1.75.0-src/src/llvm-project/llvm/lib/Demangle -I/var/tmp/portage/dev-lang/rust-host-1.75.0-r1/work/build/x86_64-pc-linux-gnu/llvm/build/include -I/var/tmp/portage/dev-lang/rust-host-1.75.0-r1/work/rustc-1.75.0-src/src/llvm-project/llvm/include -ffunction-sections -fdata-sections -fPIC --target=x86_64-pc-linux-gnu -pipe -fprofile-use=/var/tmp/portage/dev-lang/rust-host-1.75.0-r1/work/rust-pgo-1.75.0-llvm.profdata -fvisibility-inlines-hidden -w -fdiagnostics-color -ffunction-sections -fdata-sections -O3 -DNDEBUG -std=c++17  -fno-exceptions -funwind-tables -fno-rtti -MD -MT lib/Demangle/CMakeFiles/LLVMDemangle.dir/MicrosoftDemangle.cpp.o -MF lib/Demangle/CMakeFiles/LLVMDemangle.dir/MicrosoftDemangle.cpp.o.d -o lib/Demangle/CMakeFiles/LLVMDemangle.dir/MicrosoftDemangle.cpp.o -c /var/tmp/portage/dev-lang/rust-host-1.75.0-r1/work/rustc-1.75.0-src/src/llvm-project/llvm/lib/Demangle/MicrosoftDemangle.cpp
F0306 00:48:52.636827    8376 main.go:174] Command failed: rpc error: code = Internal desc = /mnt/host/source/src/chromium/depot_tools/.cipd_bin/reclient/scandeps_server terminated during startup: %!w(*command.Result=&{127 3 <nil>})
[2/2503] Building CXX object lib/Demangle/CMakeFiles/LLVMDemangle.dir/MicrosoftDemangleNodes.cpp.o
FAILED: lib/Demangle/CMakeFiles/LLVMDemangle.dir/MicrosoftDemangleNodes.cpp.o

Looks like reclient didn't like something?

vi...@google.com <vi...@google.com> #4Mar 11, 2025 07:20PM

Do you have any of the reproxy logs? Looks like it might be a dependency scanner issue.

ha...@gmail.com <ha...@gmail.com> #5Mar 11, 2025 07:34PM

I assume Raul got the those lines from this builder, so that page & linked artifacts is probably all we have?

Other CQ builders passed, but it's unclear to me if those successfully used reclient in this run, since the ebuild_logs tarball for e.g., amd64-generic-cq doesn't have a file for rust-host. I presume this extends to all host packages, which is unfortunate if so. I can add a die to check though.