Status Update
Comments
dy...@google.com <dy...@google.com>
dm...@jetbrains.com <dm...@jetbrains.com> #2
ro...@google.com <ro...@google.com>
vi...@google.com <vi...@google.com> #3
Hello Dmitry, how did you figure out that the
dm...@jetbrains.com <dm...@jetbrains.com> #4
an...@google.com <an...@google.com>
an...@google.com <an...@google.com> #5
I've submitted a fix, which will be available in an upcoming canary build of Android Studio.
an...@google.com <an...@google.com> #6
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Ladybug | 2024.1.3 Canary 3
- Android Gradle Plugin 8.7.0-alpha03
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
Description
UI thread is executing code that takes long time to finish.
The frame that is likely responsible for the freeze is jdk.accessibility@17.0.10/com.sun.java.accessibility.internal.AccessBridge$153.call(AccessBridge.java:4262).
As this is innermost frame, it is likely waiting on a synchronized object or runs for a long time without calling any other methods.
Call context:
java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:308)
jdk.accessibility@17.0.10/com.sun.java.accessibility.internal.AccessBridge$InvocationUtils$CallableWrapper.run(AccessBridge.java:7334)
jdk.accessibility@17.0.10/com.sun.java.accessibility.internal.AccessBridge$153.call(AccessBridge.java:4241)
==> jdk.accessibility@17.0.10/com.sun.java.accessibility.internal.AccessBridge$153.call(AccessBridge.java:4262) <==
Signature: freeze:jdk.accessibility@17.0.10/com.sun.java.accessibility.internal.AccessBridge$153.call-cbd3e8ca
```
####################################################
Please provide all of the following information, otherwise we may not be able to route your bug report.
####################################################
1. Forwarding a bug report from NVDA screen reader issue tracker:
3. Steps to reproduce:
3A. Start NVDA screen reader (for example, 2024.1 version)
3B. Start Android Studio without Android SDK installed.
3C. Android Studio Setup Wizard will open, on it click the Next button.
3D. Focus on the list of SDK components, press Space on one of the items to check/uncheck it.
Recording and freeze logs are attached.
Build: AI-232.10300.40.2321.11668458, 202404040104
AI-232.10300.40.2321.11668458, JRE 17.0.9+0--11185874x64 JetBrains s.r.o., OS Windows 11(amd64) v10.0 , screens 8640.0x5400.0, 5760.0x3240.0
AS: Iguana | 2023.2.1 Patch 2
Kotlin plugin: 232-1.9.0-release-358-AS10300.40.2321.11668458
Android Gradle Plugin: (plugin information not found)
Gradle: (gradle version information not found)
Gradle JDK: Oracle OpenJDK version 21.0.1
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)
```