Status Update
No update yet.
Comments
ki...@gmail.com
Weird "? extends" declarations floating in the middle of nowhere?
vi...@google.com
Thanks for the feedback. To help us troubleshoot freezes, can you please capture and share the thread dumps if this issue reproduces again?
Steps to capture the thread dumps are listed athttps://developer.android.com/studio/report-bugs#thread-dump
Steps to capture the thread dumps are listed at
ki...@gmail.com
i hope this helps
vi...@google.com
ki...@gmail.com
So i found out that this directly affected by how many activities i have.
Steps how i found that out:
1. From lagging project remove almost all activities. That's basically anything that extends AppCompatActivity.
2. Check layout file with two buttons if selecting between two buttons that 2-5 second delay still exists. (it doesn't)
3. I grabbed one of not deleted activities copied it 5 times making it six seperate classes overall.
4. Randomly coppied all these files into different sub packages. Maybe 60 classes that extends activity overall. Didn't counted.
5. Checked the same xml again. (It lagged).
p.s. I didn't added these activities to manifest file.
I will try to reproduce this behavior in sample project. When i'm done i will post results here.
Steps how i found that out:
1. From lagging project remove almost all activities. That's basically anything that extends AppCompatActivity.
2. Check layout file with two buttons if selecting between two buttons that 2-5 second delay still exists. (it doesn't)
3. I grabbed one of not deleted activities copied it 5 times making it six seperate classes overall.
4. Randomly coppied all these files into different sub packages. Maybe 60 classes that extends activity overall. Didn't counted.
5. Checked the same xml again. (It lagged).
p.s. I didn't added these activities to manifest file.
I will try to reproduce this behavior in sample project. When i'm done i will post results here.
ki...@gmail.com
Couldn't verify with new project. :(
ki...@gmail.com
Still can't reproduce with Clean project, but windows version of android studio has same issue.
Android Studio 3.6.1
Build #AI-192.7142.36.36.6241897, built on February 27, 2020
Runtime version: 1.8.0_212-release-1586-b04 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
GC: ParNew, ConcurrentMarkSweep
Memory: 1237M
Cores: 16
Registry: ide.new.welcome.screen.force=true
Non-Bundled Plugins:
Android Studio 3.6.1
Build #AI-192.7142.36.36.6241897, built on February 27, 2020
Runtime version: 1.8.0_212-release-1586-b04 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
GC: ParNew, ConcurrentMarkSweep
Memory: 1237M
Cores: 16
Registry: ide.new.welcome.screen.force=true
Non-Bundled Plugins:
di...@google.com
sr...@healthify.co
This issue is happening in latest AS also:
Android Studio 4.0.1
Build #AI-193.6911.18.40.6626763, built on June 25, 2020
Runtime version: 1.8.0_242-release-1644-b3-6222593 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 4.4.0-186-generic
GC: ParNew, ConcurrentMarkSweep
Memory: 1981M
Cores: 8
Registry:performance.watcher.unresponsive.interval.ms =0, ide.new.welcome.screen.force=true
Non-Bundled Plugins: Dart, org.jetbrains.kotlin, com.google.services.firebase, com.thoughtworks.gauge, io.flutter, org.intellij.plugins.markdown, wu.seal.tool.jsontokotlin
What I have identified is, whenever Button based Views are being edited/focused in Layout Editor, AWT-EventQueue goes haywire. I have attached video of it, before and after editing button. Please find it.
It has something to do with AWT-EventQueue, causing entire AS to hang. Tool used: JVisualVM to monitor threads.
Android Studio 4.0.1
Build #AI-193.6911.18.40.6626763, built on June 25, 2020
Runtime version: 1.8.0_242-release-1644-b3-6222593 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 4.4.0-186-generic
GC: ParNew, ConcurrentMarkSweep
Memory: 1981M
Cores: 8
Registry:
Non-Bundled Plugins: Dart, org.jetbrains.kotlin, com.google.services.firebase, com.thoughtworks.gauge, io.flutter, org.intellij.plugins.markdown, wu.seal.tool.jsontokotlin
What I have identified is, whenever Button based Views are being edited/focused in Layout Editor, AWT-EventQueue goes haywire. I have attached video of it, before and after editing button. Please find it.
It has something to do with AWT-EventQueue, causing entire AS to hang. Tool used: JVisualVM to monitor threads.
sr...@healthify.co
Please consider this as P1. Happening on Mac & Linux. It is affecting entire work, losing productivity, need to edit XML using external Text Editors. Tried enabling power save mode, disabling layout auto refresh. Nothing works. Till there is some workout around to disable the cause, it has to be P1 issue.
sr...@healthify.co
Also find threaddump before and after editing in attachment.
di...@google.com
Both thread dumps seem to be stuck at resolving the onclick listener by the properties panel. Re-assigning to Jens.
sr...@healthify.co
Hi, Is there any temporary solution/fix/workaround for this issue. Any hidden/visible configuration in Android Studio to turn off this functionality ?
sr...@healthify.co
Anyone facing this issue, found workaround for this issue:
Open Layout Editor -> Click on Attributes Tab -> Settings Icon -> Will list of options, disable all options with "Attributes", like "All Attributes", "Common Attributes", "Declared Attributes"
Disabling attributes in layout editor can avoid the freeze.
Open Layout Editor -> Click on Attributes Tab -> Settings Icon -> Will list of options, disable all options with "Attributes", like "All Attributes", "Common Attributes", "Declared Attributes"
Disabling attributes in layout editor can avoid the freeze.
jl...@google.com
Hi, thank you for reporting this issue, and thank you for the thread dump in #10.
There was an issue with the properties panel where the values of all the values in the dropdown of all attributes were computed up front on the UI thread.
This in itself may not be a problem, but if a computation for one attribute is slow (perhaps a complex app) the whole IDE will suffer.
This problem has been fixed in AS 4.1 by delaying the computation of the dropdown values until the user request to see them by interacting with a specific attribute.
Also the computation is moved to a background thread such that the user may have to wait for a slow operation to finish - but the rest of the IDE is useable while it is being computed.
There was an issue with the properties panel where the values of all the values in the dropdown of all attributes were computed up front on the UI thread.
This in itself may not be a problem, but if a computation for one attribute is slow (perhaps a complex app) the whole IDE will suffer.
This problem has been fixed in AS 4.1 by delaying the computation of the dropdown values until the user request to see them by interacting with a specific attribute.
Also the computation is moved to a background thread such that the user may have to wait for a slow operation to finish - but the rest of the IDE is useable while it is being computed.
Description
Android studio freezes for few seconds when selecting Button in layout editor. every other component works normally (i think so).
On new project this behavior is not present.
p.s. 3.5.{latest} also had this issue but it was less annoying since xml editor and layout editor was two separate things.
So my question is what could cause such behavior and how could i avoid it?
Build: AI-192.7142.36.36.6200805, 202002120909, AI-192.7142.36.36.6200805, JRE 1.8.0_212-release-1586-b4-5784211x64 JetBrains s.r.o, OS Linux(amd64) v5.3.0-29-generic, screens 2560x1440, 1920x1080AS: 3.6; Kotlin plugin: 1.3.61; Android Gradle Plugin: 3.6.0; Gradle: 5.6.4; NDK: from local.properties: 20.0.5594570, latest from SDK: 20.0.5594570; LLDB: LLDB 3.1 (revision: 3.1.4508709); CMake: from local.properties: (not specified), latest from SDK: 3.10.2, from PATH: (not found) IMPORTANT: Please read