Status Update
No update yet.
Comments
mt...@gmail.com
The same behavior has a colleague on latest Mac OS X. Same project, different PC.
Building, stop responding at:
Loading jar into dexer.
He kill java process after 15 minutes with 100% cpu ussage.
Building, stop responding at:
Loading jar into dexer.
He kill java process after 15 minutes with 100% cpu ussage.
ni...@gmail.com
This a problem of not enough java heap, so I went to shop and bought 16 gb ram
when, encreased Java Heap in gradle.properties
org.gradle.jvmargs=-Xms1024m -Xmx4096m
when, encreased Java Heap in gradle.properties
org.gradle.jvmargs=-Xms1024m -Xmx4096m
mt...@gmail.com
Thanks for #2 it helps a little with, but still, it's workaround for me, because I expect, that it show some error or crash. But not, that it will stop in some infinite loop with high cpu/mem usage.
Although same issue is on PC with 16 GB ram when I didn't set a param from #2.
Although same issue is on PC with 16 GB ram when I didn't set a param from #2.
tn...@google.com
This is because we're performing dexing in the same process as Gradle instead of in a separate process. This made builds quite a bit faster (like 30% in many cases) but if the Gradle daemon doesn't have enough memory, it makes this extremely slow instead.
In alpha8 we've added some new diagnostics which automatically turn off in-memory dexing in low memory conditions (and emits a build warning to tell you to bump up the Gradle daemon memory size as suggested in #2.)
In alpha8 we've added some new diagnostics which automatically turn off in-memory dexing in low memory conditions (and emits a build warning to tell you to bump up the Gradle daemon memory size as suggested in #2.)
fe...@gmail.com
Hi, I tried adding
org.gradle.jvmargs=-Xms1024m -Xmx4096m
in
gradle-wrapper.properties
but it doesn't work.
How should I increase Gradle daemon memory size?
Thanks!
org.gradle.jvmargs=-Xms1024m -Xmx4096m
in
gradle-wrapper.properties
but it doesn't work.
How should I increase Gradle daemon memory size?
Thanks!
cu...@gmail.com
I disable my Instant Run by
Preference -> Build -> Instant Run "Enable Instant Run to hot swap code"
I guess it is the Instant Run that make build slow and create large size pidXXX.hprof file which cause AndroidStudio gc overhead limit exceeded
Preference -> Build -> Instant Run "Enable Instant Run to hot swap code"
I guess it is the Instant Run that make build slow and create large size pidXXX.hprof file which cause AndroidStudio gc overhead limit exceeded
ak...@google.com
This is quite an old issue and is hard to provide a meaningful resolution at this point for it due to the systems involved with it changing quite a bit. Please file a new bug if you're still experiencing issues through the following link:
Description
supply all required information.
Studio Build: 2.0 preview 7
Version of Gradle Plugin: 2.0.0-alpha7
Version of Gradle:2.10
Version of Java: 1.8.0_71-15b amd64
OS: Windows 10 x64
Steps to Reproduce:
Have a huge android project with a lot of dependencies + play services - you can see gradle_dependencies.txt), android studio can not build and merge files to dex.
Java generate a big hprof file (is attached). All relevant files are in a link:
Build stuck on: 09:58:12.672 [INFO] [org.gradle.api.Project] Loading jar into dexer: C:\develop\android\sdk\build-tools\23.0.2\lib\dx.jar
Build show that failed after 5 minutes, but studio does not respond, so I can not make a complete log...
When I run build in console, it after 2 minutes finished (small sample project is compiled around 4 seconds, but our big project compile minimal 2 minutes everytime...)