Android Studio process appears to lockup indefinitely when opening project

90 views
Skip to first unread message

Joshua Soberg

unread,
Jul 10, 2015, 5:17:14 PM7/10/15
to adt...@googlegroups.com
    I have a project consisting of roughly 172 separate modules. When I attempt to open the project, Android studio appears to lock up indefinitely when initially building in gradle. When building this project from the command line, it builds without a problem (albeit taking ~10 minutes sometimes, which is somewhat expected when dealing with a project this size).

    I have attached two thread dumps from the Android Studio process (using jvisualvm), taken about 40 minutes apart from each other. There are a few similarities in these thread dumps, but one thread in particular seemed to have an interestingly long chain of recursive calls that was (almost) the same in both dumps:
"ApplicationImpl pooled thread 6" prio=4 tid=0x0000000019284000 nid=0x42f4 runnable [0x000000001eccd000]
   java.lang.Thread.State: RUNNABLE
...
at com.android.tools.idea.gradle.util.ProxyUtil.reproxy(ProxyUtil.java:143)
at com.android.tools.idea.gradle.util.ProxyUtil.reproxy(ProxyUtil.java:94)
at com.android.tools.idea.gradle.util.ProxyUtil.reproxy(ProxyUtil.java:143)
at com.android.tools.idea.gradle.util.ProxyUtil.reproxy(ProxyUtil.java:94)
at com.android.tools.idea.gradle.util.ProxyUtil.reproxy(ProxyUtil.java:143)
at com.android.tools.idea.gradle.util.ProxyUtil.reproxy(ProxyUtil.java:94)
at com.android.tools.idea.gradle.util.ProxyUtil.reproxy(ProxyUtil.java:143)
at com.android.tools.idea.gradle.util.ProxyUtil.reproxy(ProxyUtil.java:143)
at com.android.tools.idea.gradle.util.ProxyUtil.reproxy(ProxyUtil.java:143)
at com.android.tools.idea.gradle.util.ProxyUtil.reproxy(ProxyUtil.java:94)
at com.android.tools.idea.gradle.util.ProxyUtil.reproxy(ProxyUtil.java:143)
at com.android.tools.idea.gradle.IdeaAndroidProject.<init>(IdeaAndroidProject.java:91)
at com.android.tools.idea.gradle.project.AndroidGradleProjectResolver.populateModuleContentRoots(AndroidGradleProjectResolver.java:137)
at org.jetbrains.plugins.gradle.service.project.GradleProjectResolver.doResolveProjectInfo(GradleProjectResolver.java:262)
at org.jetbrains.plugins.gradle.service.project.GradleProjectResolver.access$300(GradleProjectResolver.java:63)
at org.jetbrains.plugins.gradle.service.project.GradleProjectResolver$ProjectConnectionDataNodeFunction.fun(GradleProjectResolver.java:350)
at org.jetbrains.plugins.gradle.service.project.GradleProjectResolver$ProjectConnectionDataNodeFunction.fun(GradleProjectResolver.java:322)
at org.jetbrains.plugins.gradle.service.project.GradleExecutionHelper.execute(GradleExecutionHelper.java:215)
at org.jetbrains.plugins.gradle.service.project.GradleProjectResolver.resolveProjectInfo(GradleProjectResolver.java:95)
at org.jetbrains.plugins.gradle.service.project.GradleProjectResolver.resolveProjectInfo(GradleProjectResolver.java:63)
...


    After about an hour or so of trying to let it build, Android Studio will eventually actually freeze up and leave the only option being to close it (up until this point, the loading dialog is still running). If anyone has any ideas as to why this might be locking up indefinitely, it would be greatly appreciated.
AndroidStudio_ThreadDump_01-57_July_10_2015.tdump
AndroidStudio_ThreadDump_02-35_July_10_2015.tdump

Joshua Soberg

unread,
Jul 13, 2015, 10:27:14 AM7/13/15
to adt...@googlegroups.com
For reference, I am using Android Studio version 1.2.2 (build number AI-141.1980579), and gradle version 2.2.1.

Joshua Soberg

unread,
Jul 17, 2015, 9:58:14 AM7/17/15
to adt...@googlegroups.com
I tried modifying the values in my studio64.exe.vmoptions file, and setting large enough values seemed to remedy the problem. Here are the settings that I am using for reference (The machine I'm using has 16GB of RAM):

-Xms1g
-Xmx10g
-XX:MaxPermSize=1g
-XX:ReservedCodeCacheSize=512m



On Friday, July 10, 2015 at 5:17:14 PM UTC-4, Joshua Soberg wrote:

Alex Ruiz

unread,
Jul 17, 2015, 1:39:15 PM7/17/15
to adt...@googlegroups.com
Hi Joshua,

The issue seems to be in the way to build a proxy for future caching of the Android model (the purpose is to, ironically, improve performance of the IDE).

I'll investigate this issue and I'll keep this thread updated with any progress.

Regards,
-Alex

--
You received this message because you are subscribed to the Google Groups "adt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to adt-dev+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Alex Ruiz

unread,
Jul 17, 2015, 1:45:43 PM7/17/15
to adt...@googlegroups.com
It has been fixed in 1.3. (I'm double-checking with a big project)

Joshua Soberg

unread,
Jul 17, 2015, 2:12:21 PM7/17/15
to adt...@googlegroups.com
Alex,

    Thank you for the input. I began using the canary builds rather than the stable builds, and along with the vmoptions changes described above I don't seem to be having any more trouble opening my project.

Thank you,
    Josh
Reply all
Reply to author
Forward
0 new messages