Develop Reference

Jenkins gradle daemons can't seem to be re-used or cleaned up and crashes system after couple of consecutive builds

I've got Jenkins configured for running about 50 consecutive app builds, but somehow after a build or 7-10 the heap seems to get flooded, occasionally crashing my system.
The Jenkins console output would show me something like:
Starting a Gradle Daemon, 4 stopped Daemons could not be reused
And if i open the Task Manager (on Windows) i can see that Jenkins keeps starting similar 'Open JDK Platform Binary' processes (more than 15!), but can't seem to clean them up and this is what eventually causes occasionally a system crash, but most of the time the next build to not be able to succeed.
Giving me a console log message like:
What went wrong:
Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the User Manual chapter on the daemon at https://docs.gradle.org/5.5/userguide/gradle_daemon.html
Process command line: C:\Program Files\Android\Android Studio\jre\bin\java.exe -XX:MaxHeapSize=4g -Xmx4g -Dfile.encoding=windows-1252 -Duser.country=US -Duser.language=en -Duser.variant -cp C:\Gradle\gradle-5.5\lib\gradle-launcher-5.5.jar org.gradle.launcher.daemon.bootstrap.GradleDaemon 5.5
Please read the following process output to find out more:
Error occurred during initialization of VM
Unable to allocate 131072KB bitmaps for parallel garbage collection for the requested 4194304KB heap.
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Does anyone know how to fix this?

How to fix 'java.lang.module.FindException: module java.se.ee not found' error when packaging my kivy application with buildozer

I'm trying package my kivy app (python3) but when i run the command buildozer -v android debug see this error
# Cwd /home/javier/.buildozer/android/platform/android-sdk
Error occurred during initialization of boot layer
java.lang.module.FindException: Module java.se.ee not found
# Command failed: /home/javier/.buildozer/android/platform/android-sdk/tools/bin/sdkmanager tools platform-tools
#
# Buildozer failed to execute the last command
# The error might be hidden in the log above this error
# Please read the full log, and search for it before
# raising an issue with buildozer itself.
# In case of a bug report, please add a full log with log_level = 2
I have this Java version
$ java --version
openjdk 11.0.2 2019-01-15
OpenJDK Runtime Environment (build 11.0.2+9-Ubuntu-3ubuntu118.04.3)
OpenJDK 64-Bit Server VM (build 11.0.2+9-Ubuntu-3ubuntu118.04.3, mixed mode, sharing)
I downloaded only sdkmanager Command line tools from here and put it in my root path but i don't had success.
I Saw in this post a solution and i did it but i don't solve the error.
I has a virtualenv with all dependencies installed. Also i edited the buildozer.spec and i was custom it
The Virtualenv is:
(envAppSinapsis)~/AppSin$ pip freeze
certifi==2019.3.9
chardet==3.0.4
Cython==0.28.2
docutils==0.14
idna==2.8
Kivy==1.10.1
Kivy-Garden==0.1.4
psycopg2==2.7.6.1
psycopg2-binary==2.7.6.1
pygame==1.9.4.dev0
Pygments==2.3.1
requests==2.21.0
urllib3==1.24.1
I think that error is related to something related to JAVA but I do not know what. I would appreciate your helps, and please, excuse my bad English.
I am working in Ubuntu 18
UPDATE
Print Screen Error

Up until a few days ago if you had installed openjdk-11-jdk/jre from the Ubuntu repos you would have found it was actually a version of Java 10 (https://askubuntu.com/questions/1037646/why-is-openjdk-10-packaged-as-openjdk-11).
java.se.ee has been deprecated in Java 9, 10 and removed in Java 11 (https://www.oracle.com/technetwork/java/javase/11-relnote-issues-5012449.html)
Unfortunately there is no simple way to get the Android tools like sdkmanager or avdmanager running with Java 11 yet.
I was able to get buildozer running on Ubuntu again with Java 10:
Download Java 10 Linux x64 JDK (.tar.gz) from http://jdk.java.net/java-se-ri/10
Untar: tar -xzvf jdk-10_linux-x64_bin_ri.tar.gz
Set PATH: export PATH=/path/to/inflated/jdk-10/bin:$PATH

was getting error License not accepted for SDK Build tools etc
solved by Installing
SDK Command Line Tools
Google Play licensing services
in SDK Manager > SDK Tools
helped me after getting frustrated for 2 hours, and hearing from everyone that only way is to downgrade Java

You can solve this error by downgrading Java or by executing the below command in your terminal.
export JAVA_OPTS='-XX:+IgnoreUnrecognizedVMOptions --add-modules java.se.ee'
Also, don't download the platform tools yourself, let buildozer take care of that.
If the above command doesn't work try deleting the buildozer files from your app and rebuilding your application.

Gradle daemon unable to start jvm no Xmx1024 or any other error

I Have Tried A Many ways To Do Successful Gradle Build
Tried A Lott Of Ways online But I can't Even I Have Changed org.gradle.jvmargs=-Xmx5124m
Toorg.gradle.jvmargs=-Xmx1024m
To
org.gradle.jvmargs=-Xmx512m
Unable to start the daemon process
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at https://docs.gradle.org/4.4/userguide/gradle_daemon.html
Please read the following process output to find out more:
-----------------------
.
PC Info:
OS:Windows 8
Android Studio 3.1.4
Build #AI-173.4907809, built on July 23, 2018
JRE: 1.8.0_152-release-1024-b02 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 8.1 6.3

You can go to .gradle folder in your $USER_HOME and delete all the directories except wrapper. then build again in android studio and it will generate deamon again

Gradle build runs forever on a clean install and an empty project

Gradle builds run forever and I can't figure out why.
I have installed Android Studio on Ubuntu 15.04. It is set up with all of the default options from the wizard.
I have created an empty project and I have not added any code. When I attempt to build the project a gradle process starts up but never terminates. I have tried letting it run for an hour but there was no progress. I end up having to manually kill gradle in order to close Android Studio. (via "ps aux | grep gradle; kill -9 ")
I am using open-jdk 1.7, but I have also tried using oracle java (with the same results).
My desktop has 32 GB ram. I have attempted increasing the amount of memory allocated to Android Studio to no effect.
My CPU has AMD-64 architecture. Although I couldn't find anything on google suggesting this was the cause of my woes, could it be responsible?
There are no error messages that appear in the terminal when I run studio.sh manually. Below is the terminal output (annotated by me):
#starting Android Studio
Starting a new Gradle Daemon for this build (subsequent builds will be faster).
Starting process 'command '/usr/lib/jvm/java-1.7.0-openjdk-amd64/bin/java''. Working directory: /home/cody/Documents/AndroidStudio/MyApplication Command: /usr/lib/jvm/java-1.7.0-openjdk-amd64/bin/java -version
Successfully started process 'command '/usr/lib/jvm/java-1.7.0-openjdk-amd64/bin/java''
#gradle starts up, this never terminates unless I terminate it myself
Starting daemon process: workingDir = /home/cody/.gradle/daemon/2.4, daemonArgs: [/usr/lib/jvm/java-1.7.0-openjdk-amd64/bin/java, -XX:MaxPermSize=256m, -XX:+HeapDumpOnOutOfMemoryError, -Xmx1024m, -Dfile.encoding=UTF-8, -Duser.country=US, -Duser.language=en, -Duser.variant, -cp, /home/cody/.gradle/wrapper/dists/gradle-2.4-all/6r4uqcc6ovnq6ac6s0txzcpc0/gradle-2.4/lib/gradle-launcher-2.4.jar, org.gradle.launcher.daemon.bootstrap.GradleDaemon, 2.4, /home/cody/.gradle, /home/cody/.gradle/daemon, 10800000, fb6e1111-7ac5-4afc-9630-890712f3195f, -XX:MaxPermSize=256m, -XX:+HeapDumpOnOutOfMemoryError, -Xmx1024m, -Dfile.encoding=UTF-8, -Duser.country=US, -Duser.language=en, -Duser.variant]Starting process 'Gradle build daemon'. Working directory: /home/cody/.gradle/daemon/2.4 Command: /usr/lib/jvm/java-1.7.0-openjdk-amd64/bin/java -XX:MaxPermSize=256m -XX:+HeapDumpOnOutOfMemoryError -Xmx1024m -Dfile.encoding=UTF-8 -Duser.country=US -Duser.language=en -Duser.variant -cp /home/cody/.gradle/wrapper/dists/gradle-2.4-all/6r4uqcc6ovnq6ac6s0txzcpc0/gradle-2.4/lib/gradle-launcher-2.4.jar org.gradle.launcher.daemon.bootstrap.GradleDaemon 2.4 /home/cody/.gradle /home/cody/.gradle/daemon 10800000 fb6e1111-7ac5-4afc-9630-890712f3195f -XX:MaxPermSize=256m -XX:+HeapDumpOnOutOfMemoryError -Xmx1024m -Dfile.encoding=UTF-8 -Duser.country=US -Duser.language=en -Duser.variant
Successfully started process 'Gradle build daemon'
An attempt to start the daemon took 0.99 secs.
Connected to daemon DaemonInfo{pid=9307, address=[98dcf537-f8f6-4e74-ad4d-c57a86d4a6c1 port:48946, addresses:[/0:0:0:0:0:0:0:1%1, /127.0.0.1]], idle=false, context=DefaultDaemonContext[uid=fb6e1111-7ac5-4afc-9630-890712f3195f,javaHome=/usr/lib/jvm/java-7-openjdk-amd64,daemonRegistryDir=/home/cody/.gradle/daemon,pid=9307,idleTimeout=10800000,daemonOpts=-XX:MaxPermSize=256m,-XX:+HeapDumpOnOutOfMemoryError,-Xmx1024m,-Dfile.encoding=UTF-8,-Duser.country=US,-Duser.language=en,-Duser.variant]}. Dispatching request Build{id=0ec396f9-4092-4fd1-93c4-0837d861cb85.1, currentDir=/home/cody/Documents/AndroidStudio/MyApplication}.
#I manually kill gradle
The message received from the daemon indicates that the daemon has disappeared.

Try sudo apt-get install lib32z1 as in this post. I had the same problem on Lubuntu and fixed it this way.

In my case, i already had lib32z1 installed. The problem was Genymotion plugin. Once i removed it from studio and restarted. It worked fine. I still don't know how that could happen as i regularly use genymotion with studio in my other machines. You can still run genymotion even if you remove studio plugin by starting emulator from genymotion itself.

I have centos 7 64 bits installed on a virtualbox 5.0.16 virtual machine and gradle version 2.10 with Android Studio 2.0
The log file of gradle is located at $HOME/.gradle/daemon/2.10
Log file: daemon-<some number>.out.log
By inspecting this log file I found out that libz.so.1 was not found by aapt.
Despite that command "locate libz.so.1" output was
/usr/lib64/libz.so
/usr/lib64/libz.so.1
/usr/lib64/libz.so.1.2.7
aapt was not able to find it.
In order to solve the issue I had to execute
yum install zlib.i686
After that Gradle started working.

VM error while Build Cordova PhoneGap

I got this error while i tried to create a Cordova PhoneGap application, and in the final step while I use the build command
cordova build android
I got this error:
Error
D:\rmapp>cordova run android
Running command: D:\rmapp\platforms\android\cordova\run.bat
ANDROID_HOME=D:\Android\sdk
JAVA_HOME=C:\Program Files (x86)\Java\jdk1.7.0_71
WARNING : No target specified, deploying to device '192.168.56.100:5555'.
Running: D:\rmapp\platforms\android\gradlew cdvBuildDebug -b D:\rmapp\platform
s\android\build.gradle -PcdvBuildArch=x86 -Dorg.gradle.daemon=true
FAILURE: Build failed with an exception.
* What went wrong:
Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at http://gradle.org/docs/2
.2.1/userguide/gradle_daemon.html
Please read the following process output to find out more:
-----------------------
Error occurred during initialization of VM
Could not reserve enough space for object heap
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug
option to get more log output.
D:\rmapp\platforms\android\cordova\node_modules\q\q.js:126
throw e;
^
Error code 1 for command: cmd with args: /s /c "D:\rmapp\platforms\android\grad
lew cdvBuildDebug -b D:\rmapp\platforms\android\build.gradle -PcdvBuildArch=x86
-Dorg.gradle.daemon=true"
ERROR running one or more of the platforms: Error: D:\rmapp\platforms\android\c
ordova\run.bat: Command failed with exit code 1
You may not have the required environment or OS to run this project

Your system can not provide enough continuous memory space for the jvm and causes the problem.
Here is what works for me:
Add an environment variable GRADLE_OPTS with the value of -Dorg.gradle.jvmargs=-Xmx512m
You can use -Xmx1g if you have more memory space available.

Close Visual Studio -- at least this was the problem in my case.
and/or any other memory intensive program.

My JAVA_HOME was defaulting to the x86 version. Adding a new JAVA_HOME variable in the System env variable and pointing it to the x64 version worked for me. This was the path I ended up with:
C:\Program Files\Java\jdk1.8.0_162

I had the same problem too. Try to run command line with administrative privileges.

just solved this problem in windows 8.1 and windows 7. Here is what I did:
Uninstall everything that is java related in your Programs and Features in control panel
check the following directory and delete the java folders:
a. c:\users\\AppData\Local\Oracle
b. c:\users\\AppData\LocalLow\Oracle
c. c:\Program Files\Java
d. C:\Program Files (x86)\Java
e. C:\ProgramData\Oracle
**IMPORTANT: only delete this folders after successfully uninstalling all java entries in control panel > Programs and Features
Download and install the latest Java SDK from here
After all you are done go to cmd(run as admin) and try to build again
conclusion: from what I understand, I do not have java properly configured/installed in my machine. so a clean install of everything is what solved my problem.

I got this error even if I used 2 gigs (-Dorg.gradle.jvmargs=-Xmx2048m), but it started to work when I changed JAVA_HOME to a 64-bit JDK directory. Using a higher version of Java might help also (1.8+).

Change argument -Xmx20484m to 1024 at line:
args.push('-Dorg.gradle.jvmargs=-Xmx1024m');
in your project file
platforms\android\cordova\lib\builders\GradleBuilder.js
.
It's work for me
https://forum.ionicframework.com/t/build-failed-unable-start-the-daemon-process/72171
It work for me in eclipce phonegap plugin

In Environment variables, add a system variable _JAVA_OPTIONS having the value -Xmx512M.

Run the following command in CLI with admin right.
>export _JAVA_OPTIONS="-Xmx256M"
This happens to me on machines with a lot of ram, but with lower memory ulimits. Java decides to allocate a big heap because it detects the ram in the machine, but it's not allowed to allocate it because of ulimits.

I had the same problem while I was working on Cordova.
As mentioned in this post, it looks like the heap is not allocated and so the JVM isn't initialized.
Try to free your system cache and then try building the project.

This error happens to me from time to time. I fix this by running the program "SDK Manager" in ANDROID_HOME folder.

I got this error because I didn't have a 32-bit JDK installed. Installed that, restarted and that fixed it.

My solution was to just install the new Java SDK. I also had to change my JAVA_HOME Path to point to that new SDK

I had had the same problem with my cordova project when I have installed the last version of JDK 1.8.0.121.
To solve the problem, I have uninstalled all my JDK versions (1.6, 1.7, 1.8..) and just installed the last version.

Install 64bit version of Java JDK and point JAVA_HOME to the install dictionary.

I had a very similar problem that sometimes logged this JAVAC error and other times logged device connection problems or plugin not correctly installed. Ex:
Failed to run "javac -version"
Execute program failed with exit code 3221225794.
I successfully fixed it by running the following command that fixes all DLL problems on Windows, and then restarting the computer.
From powershell, admin may be required:
sfc /scannow

You need to allocate memory by setting two environment variables:
_JAVA_OPTIONS with value -Xmx2048M, to set up how much memory Java uses
GRADLE_OPTS with value -Dorg.gradle.jvmargs=-Xmx2048m, to set up how much memory Gradle uses (this can be specified by per project basis through [PROJECT PATH]\platforms\android\cordova\lib\builders\GradleBuilder.js path, although by default it's setup to be 2GB atm)
If cordova complains with Failed to run "javac -version" change the memory in _JAVA_OPTIONS for something lower.