Hi everybody, I am running assembleDebug on a build machine (CircleCI, actually) and it is using up way too much RAM, which ends up causing my build to di.
This appears to be because preDexDebug launches many processes. On my build machine, which is running Ubuntu this number is about 35, and here's an example line: ubuntu 17521 10450 12 22:28 pts/4 00:00:05 /usr/lib/jvm/jdk1.8.0/bin/java -Xmx1024M -Dfile.encoding=UTF-8 -Duser.country=US -Duser.language=en -Duser.variant -cp /usr/local/android-sdk-linux/build-tools/21.1.2/lib/dx.jar com.android.dx.command.Main --dex --multi-dex --output /home/ubuntu/android/android/my_company/build/intermediates/pre-dexed/dev/debug/library-1.0.17-a69076f503290a370c22f778775cce2b2b8033b8.jar /home/ubuntu/.gradle/caches/modules-2/files-2.1/com.mcxiaoke.volley/library/1.0.17/f417d7f776d1ee5858fc04d9362aa45e9bedd26b/library-1.0.17.jar Each one of these ends up taking 100-200MB of memory and thus, cumulatively, I easily hit the 4GB limit that CircleCI imposes. However when I run the build on my Mac only about 10 processes seem to spring up. Is there any way to control this parallelism so I can keep from allocating so much memory? Thanks, Mike -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
