Fixed
Status Update
No update yet.
Comments
[Deleted User] <[Deleted User]>
Also happens in 3.2 Beta 4.
uc...@google.com
Reproducible in
Android Studio 3.3 Canary 3
Build #AI-181.5281.24.33.4884283, built on July 10, 2018
JRE: 1.8.0_152-release-1136-b04 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 4.9.0-6-amd64
Android Studio 3.3 Canary 3
Build #AI-181.5281.24.33.4884283, built on July 10, 2018
JRE: 1.8.0_152-release-1136-b04 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 4.9.0-6-amd64
al...@google.com
[Deleted User] <[Deleted User]>
Same problem with android studio 3.2 stable. 3.1 was fine. In our case only applications with cpp integration showing this issue.
Build: 3.2, AI-181.5540.7.32.5014246, 201809171917,
AI-181.5540.7.32.5014246, JRE 1.8.0_152-release-1136-b06x64 JetBrains s.r.o, OS Mac OS X(x86_64) v10.14 unknown, screens 2560x1440, 1920x1200; Retina
Android Gradle Plugin: 3.2.0
Gradle: 4.10.2
NDK: from local.properties: 16.1.4479499; latest from SDK: 18.0.5002713;
LLDB: LLDB 3.1 (revision: 3.1.4508709)
CMake: from local.properties: (not specified); latest from SDK: 3.6.0-rc2; from PATH: 3.11.1;
Build: 3.2, AI-181.5540.7.32.5014246, 201809171917,
AI-181.5540.7.32.5014246, JRE 1.8.0_152-release-1136-b06x64 JetBrains s.r.o, OS Mac OS X(x86_64) v10.14 unknown, screens 2560x1440, 1920x1200; Retina
Android Gradle Plugin: 3.2.0
Gradle: 4.10.2
NDK: from local.properties: 16.1.4479499; latest from SDK: 18.0.5002713;
LLDB: LLDB 3.1 (revision: 3.1.4508709)
CMake: from local.properties: (not specified); latest from SDK: 3.6.0-rc2; from PATH: 3.11.1;
[Deleted User] <[Deleted User]>
It is happening quite a lot in:
Android Studio 3.4 Canary 9
Build #AI-183.4588.61.34.5186062, built on December 17, 2018
JRE: 1.8.0_152-release-1248-b22 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.13.6
I can watch it when I first load a large-ish (10 modules, 4 with source code and the remainder are just binary .aar modules) for 30 seconds or so, it looks somewhat like it's running through some list of open and close directory tree operations, perhaps from my editing history?
I am on the 'Android' project project window menu entry (not sure what to call that, scope? subscope?)
Android Studio 3.4 Canary 9
Build #AI-183.4588.61.34.5186062, built on December 17, 2018
JRE: 1.8.0_152-release-1248-b22 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.13.6
I can watch it when I first load a large-ish (10 modules, 4 with source code and the remainder are just binary .aar modules) for 30 seconds or so, it looks somewhat like it's running through some list of open and close directory tree operations, perhaps from my editing history?
I am on the 'Android' project project window menu entry (not sure what to call that, scope? subscope?)
[Deleted User] <[Deleted User]>
Just fired up:
Android Studio 3.4 Canary 10
Build #AI-183.4588.61.34.5202479, built on December 27, 2018
JRE: 1.8.0_152-release-1248-b22 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.13.6
And captured a movie of what happens whenever the project is reloaded.
Android Studio 3.4 Canary 10
Build #AI-183.4588.61.34.5202479, built on December 27, 2018
JRE: 1.8.0_152-release-1248-b22 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.13.6
And captured a movie of what happens whenever the project is reloaded.
[Deleted User] <[Deleted User]>
Compared with another developer on the same project, and found two things:
1) His project view doesn't jump around like it is possessed.
2) My project view only jumps around in Android mode, not in Project mode.
So, I'm not sure why mine is doing this, I can only assume some cross-contamination of previous settings. So I'm going to make a clean installation and try that. I'll back up my settings first, if I can figure out how to.
1) His project view doesn't jump around like it is possessed.
2) My project view only jumps around in Android mode, not in Project mode.
So, I'm not sure why mine is doing this, I can only assume some cross-contamination of previous settings. So I'm going to make a clean installation and try that. I'll back up my settings first, if I can figure out how to.
[Deleted User] <[Deleted User]>
Fresh install, deleted preferences and settings from Library, same issue.
Must be something in the .idea directory of my project. Deleted that, recovered from the problems that creates. Still happens.
Must be something in the .idea directory of my project. Deleted that, recovered from the problems that creates. Still happens.
so...@google.com
The most frequent case when it could happen was related to sync process completely resetting the state of the project. It has been fixed in 3.6 builds.
so...@google.com
an...@gmail.com
It's been a year now, when is it going to get fixed ? My project has 50+ library modules, 10+ app modules and it goes unusable for several minutes, upon each sync which itself now last 6+ minutes!
So on every little change, such as changing app version number (automatically added to gradle files, which I had to remove), it's about 10 minutes without being able to do anything.
So on every little change, such as changing app version number (automatically added to gradle files, which I had to remove), it's about 10 minutes without being able to do anything.
so...@google.com
Could you please let us know if you observe the same problem in 3.6 beta 1 and if so any details of when it happens in 3.6?
[Deleted User] <[Deleted User]>
Yes. 3.6 RC1 is showing this sort of behaviour, where after the indexing pass, when you are showing the Android tab inside the project window in Android Studio, the directory tree will open and close, and repaint several times. I would say this is quite common to see, even on 4.0.0-alphaX builds of Android Studio. There also seems to be a small indeterminate progress bar in the top right of the window that often gets stuck in a rotating condition, and sometimes I've had to restart AS to get rid of it.
so...@google.com
Thank you for the feedback. We have identified several more causes of this behaviour and are working to eliminate them.
so...@google.com
I think I found the root cause. While opening/syncing a project we may temporarily represent an android module as a java module which completely changes the underlying tree structure. We should be able to not do it now.
I have a project that reliably shows this behaviour.
so...@google.com
The most common cause of flickering, which is changing the type of tree node without updating the tree model, has been fixed. Java and Android modules do not change their type while opening/syncing a project any longer and all the workarounds making them equal (they were not because of the different structure of their children) have been removed. There might still be the case down the hierarchy with a similar problem.
Please open a new bug if you still experience the problem in 4.0 beta (after canary 9) builds.
so...@google.com
an...@gmail.com
Still occurring in 4.0.1, less frequently but still there.
For example, copying an xml layout from main to a different variant just created the issue.
For example, copying an xml layout from main to a different variant just created the issue.
Description
AI-181.5281.24.32.4860949, JRE 1.8.0_152-release-1136-b04x64 JetBrains s.r.o, OS Mac OS X(x86_64) v10.13.5 unknown, screens 2560x1440, 1440x900
Android Gradle Plugin: 3.2.0-beta02
Gradle: 4.6
I don't remember this happening before, but whenever I switch branches or do a Gradle Sync, often the Project>Android tree refreshes many dozens of times. I had thought this might be related to the .idea/workspace.xml so I would delete that and restart the IDE, but that doesn't seem to stop this from happening. I've disabled workspace resuming when switching branches, but that doesn't stop this behaviour. Sorry, I can't really explain this very well. I'll try and attach a movie to show this.