Profiler: sometimes Spacebar tries to close the trace instead of panning, super annoying. [319805747]

Bug

Status Update

No update yet.

Description

di...@gmail.com

created issue #1

Jan 12, 2024 10:11PM

####################################################

Please provide all of the following information, otherwise we may not be able to route your bug report.

####################################################


1. Describe the bug or issue that you're seeing.
Sometimes holding spacebar to pan doesn't work, and instead tries to close the trace. This is super obnoxious and frustating. The issues appears to be that the trace window isn't focused, and the focus gets stuck on the red "Stop" button. However, clicking into the trace window doesn't focus it. To make this problem even more dumb, sometimes clicking into the trace window has other undesirable effects even if it isn't focused, like it enters some kind of selection mode and draws a light grey box over some of the events. The UI is also very laggy, the whole experience is barely usable at all.

Desired behavior: holding spacebar should switch the profiler tool to "pan", and clicking into empty space in the profiler window should focus the window without entering strange selection modes.

2. Attach log files from Android Studio
  2A. In the IDE, select the Help..Collect Logs and Diagnostic Data menu option.
  2B. Create a diagnostic report and save it to your local computer.
  2C. Attach the report to this bug using the Add attachments button.

3. If you know what they are, write the steps to reproduce:

   3A.
   3B.
   3C.

In addition to logs, please attach a screenshot or recording that illustrates the problem.

For more information on how to get your bug routed quickly, see https://developer.android.com/studio/report-bugs.html

Build: AI-231.9392.1.2311.11076708, 202311091110

AI-231.9392.1.2311.11076708, JRE 17.0.7+0-17.0.7b1000.6-10550314x64 JetBrains s.r.o., OS Mac OS X(x86_64) v14.2.1, screens 2560.0x1440.0, 3584.0x2240.0, 1440.0x2560.0; Retina

AS: Hedgehog | 2023.1.1
Kotlin plugin: 231-1.9.10-release-459-AS9392.1.2311.11076708
Android Gradle Plugin: 8.1.0
Gradle: 8.2.1
Gradle JDK: JetBrains Runtime version 17.0.7
NDK: from local.properties: (not specified), latest from SDK: (not found)
CMake: from local.properties: (not specified), latest from SDK: (not found), from PATH: (not found)

Comments

ad...@google.com <ad...@google.com> Jan 12, 2024 10:14PM

Assigned to an...@google.com.

sh...@google.com <sh...@google.com> Jan 16, 2024 07:06PM

Status: New

ad...@google.com <ad...@google.com> #2Jan 17, 2024 08:38PM

Assigned to di...@gmail.com.

This functionality was released in benchmark 1.2.0-alpha06: https://developer.android.com/jetpack/androidx/releases/benchmark#1.2.0-alpha06

You'll need to use an Android 13 (API 33) emulator, and androidx.benchmark:benchmark-macro-junit4:1.2.0-alpha06, which removes the requirement for root, and thus works on Play emulator images.

or...@gmail.com <or...@gmail.com> #3Jan 18, 2024 01:51AM

You can find details of my OS in my original post, I'm running OS X x86 v14.2.1, it happens frequently, and the issue is quite clear from my description. Have you tried to reproduce it yet? I don't feel a video is necessary here, and unfortunately I don't have the time to make a video for every bug.

yd...@google.com <yd...@google.com> #4Jan 24, 2024 07:45PM

We apologize for any inconvenience this bug has caused. Upon reproducing this, we have found that this is caused by default accessibility feature behavior. One work around is to click the "Summary" tab to reset focus in trace view. Please let us know if that works for you!

di...@gmail.com <di...@gmail.com> #5Jan 24, 2024 09:09PM

Thanks for the info, that does work! I'll have to remember what to do when this does happen, but it's definitely better than nothing.

yd...@google.com <yd...@google.com> Aug 21, 2024 06:29PM