Daemon (setup failed)

Status

Fixed

Issue description

Issue comments

The first option would be to restart the computer and try again. If this does not help, try disabling daemon mode in Gradle settings in Preferences, as they don't take RAM changes too well. After you set it up and find a good RAM value, you can turn on the daemon mode again.

Executing gradle command: cleanCache clean setupDecompWorkspace --refresh-dependencies
Build info: MCreator 1.8.0, 64-bit, 16342 MB, Windows 10, JVM 1.8.0_172
(c) 2018 Microsoft Corporation. Tutti i diritti sono riservati.
C:\Pylo\MCreator180\forge>gradlew -Dorg.gradle.daemon=true -Dorg.gradle.parallel=false -Dorg.gradle.jvmargs="-Xms1024m -Xmx2048m" cleanCache clean setupDecompWorkspace --refresh-dependencies
Starting a new Gradle Daemon for this build (subsequent builds will be faster).
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 https://docs.gradle.org/2.14/userguide/gradle_daemon.html
Please read the following process output to find out more:
-----------------------
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
C:\Pylo\MCreator180\forge>
Task completed with return code 0 in 3825 milliseconds

Executing gradle command: cleanCache clean setupDecompWorkspace --refresh-dependencies
Build info: MCreator 1.8.0, 64-bit, 16342 MB, Windows 10, JVM 1.8.0_172
(c) 2018 Microsoft Corporation. Tutti i diritti sono riservati.
C:\Pylo\MCreator180\forge>gradlew -Dorg.gradle.daemon=true -Dorg.gradle.parallel=false -Dorg.gradle.jvmargs="-Xms1024m -Xmx2048m" cleanCache clean setupDecompWorkspace --refresh-dependencies
Starting a new Gradle Daemon for this build (subsequent builds will be faster).
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 https://docs.gradle.org/2.14/userguide/gradle_daemon.html
Please read the following process output to find out more:
-----------------------
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
C:\Pylo\MCreator180\forge>
Task completed with return code 0 in 3096 milliseconds

Executing gradle command: cleanCache clean setupDecompWorkspace --refresh-dependencies
Build info: MCreator 1.8.0, 64-bit, 16342 MB, Windows 10, JVM 1.8.0_172
(c) 2018 Microsoft Corporation. Tutti i diritti sono riservati.
C:\Pylo\MCreator180\forge>gradlew -Dorg.gradle.daemon=true -Dorg.gradle.parallel=false -Dorg.gradle.jvmargs="-Xms1024m -Xmx2048m" cleanCache clean setupDecompWorkspace --refresh-dependencies
Starting a new Gradle Daemon for this build (subsequent builds will be faster).
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 https://docs.gradle.org/2.14/userguide/gradle_daemon.html
Please read the following process output to find out more:
-----------------------
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
C:\Pylo\MCreator180\forge>
Task completed with return code 0 in 2992 milliseconds

Set min RAM to lower value, around 2GB should work.

Make sure you don't have any JAVA_HOME variables pointing to 32 bit Java versions too. If this is the case and you can't change it, set the RAM somewhere below 4GB.

These forums topics might help too:

Plugin Java 11.191.2.12 x86
Uso della versione JRE 1.8.0_191-b12 Java HotSpot(TM) Client VM
Directory home utente = C:\Users\*************
----------------------------------------------------
Initializing applet
Version: 1.8.0_191
Vendor: Oracle+Corporation
OS: Windows+10
OS Version: 10.0
Called setUserInfo
Ending init

(it's ok?)

You don't have to reply with the same error each time. I don't have other ideas what could be causing this, sorry.

i change ram, daemon settings, .... and it still not work

i tried to download old version of mcreator but still doesn't work

If I would have any other idea on how to fix this bug, I would be very glad to provide you tips but I don't have any other ideas on what could be causing this error.

i have a oracle virtual box and i tried to download mcreator on my wirtual box (win 7) and it works but only on my virtual box

so the problem is my pc but one week ago it worked

Most likely you did a configuration change in the computer (settings, new software, etc.) that caused this error. If you have will and time, you might want to reinstall OS, but it the VirtualBox solutions works for you, you could get away with this too.

new error:

Executing gradle command: --stacktrace
Build info: MCreator 1.8.0, 64-bit, 16342 MB, Windows 10, JVM 1.8.0_172
(c) 2018 Microsoft Corporation. Tutti i diritti sono riservati.
C:\Pylo\MCreator180\forge>gradlew -Dorg.gradle.daemon=false -Dorg.gradle.parallel=false -Dorg.gradle.jvmargs="-Xms625m -Xmx2048m" --stacktrace
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 https://docs.gradle.org/2.14/userguide/gradle_daemon.html
Please read the following process output to find out more:
-----------------------
* Try:
Run with --info or --debug option to get more log output.
* Exception is:
org.gradle.api.GradleException: 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/2.14/userguide/gradle_daemon.html
Please read the following process output to find out more:
-----------------------
   at org.gradle.launcher.daemon.bootstrap.DaemonGreeter.parseDaemonOutput(DaemonGreeter.java:34)
   at org.gradle.launcher.daemon.client.DefaultDaemonStarter.startProcess(DefaultDaemonStarter.java:153)
   at org.gradle.launcher.daemon.client.DefaultDaemonStarter.startDaemon(DefaultDaemonStarter.java:136)
   at org.gradle.launcher.daemon.client.DefaultDaemonConnector.startDaemon(DefaultDaemonConnector.java:111)
   at org.gradle.launcher.daemon.client.SingleUseDaemonClient.execute(SingleUseDaemonClient.java:52)
   at org.gradle.launcher.daemon.client.SingleUseDaemonClient.execute(SingleUseDaemonClient.java:37)
   at org.gradle.launcher.cli.RunBuildAction.run(RunBuildAction.java:43)
   at org.gradle.internal.Actions$RunnableActionAdapter.execute(Actions.java:173)
   at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:239)
   at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:212)
   at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:35)
   at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:24)
   at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33)
   at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22)
   at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:205)
   at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:169)
   at org.gradle.launcher.Main.doAction(Main.java:33)
   at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:498)
   at org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:55)
   at org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:36)
   at org.gradle.launcher.GradleMain.main(GradleMain.java:23)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:498)
   at org.gradle.wrapper.BootstrapMainStarter.start(BootstrapMainStarter.java:30)
   at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:127)
   at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:61)
C:\Pylo\MCreator180\forge>
Task completed with return code 0 in 2385 milliseconds

:( why :( a week ago it worked :( D:

I got another idea. Try going to your user home folder, then in .mcreator folder and delete gradle folder in this folder. Then try to install MCreator again.

now??

I am very sory to say this but I ran out of ideas. If it works for you, you could use VirtualBox or try to use another computer.

yee fixed with new forge update

!!!!!!!

Glad to hear you got this working :)