Stuck on Caching Code To Improve Performance

Started by EnderMagnet on

Topic category: Troubleshooting, bugs, and solutions

EnderMagnet
Joined Aug 2017
Points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • MCreator plugins:
  • Comments:
Stuck on Caching Code To Improve Performance

I'VE LOOKED AT LOT'S OF OTHER SIMILAR BUG REPORTS BUT NONE SEEM TO WORK!

Every time I run MCreator it gets stuck on Caching Decompiled code: Caching Code To Improve Performance and I don't know what to do. This is what to console tab reads:

Executing gradle command: wrapper --gradle-version 4.4
Build info: MCreator 1.8.3, 64-bit, 16340 MB, Windows 10 - cmd, JVM 1.8.0_202, JAVA_HOME: C:\Pylo\MCreator183\jdk
C:\Pylo\MCreator183\forge>gradlew -Dorg.gradle.java.home="C:/Pylo/MCreator183/jdk" -Dorg.gradle.parallel=false -Dorg.gradle.jvmargs="-Xms4095m -Xmx4095m" wrapper --gradle-version 4.4 
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\MCreator183\forge>
Task completed with return code 0 in 2420 milliseconds
   
Executing gradle command: setupDecompWorkspace --refresh-dependencies
Build info: MCreator 1.8.3, 64-bit, 16340 MB, Windows 10 - cmd, JVM 1.8.0_202, JAVA_HOME: C:\Pylo\MCreator183\jdk
C:\Pylo\MCreator183\forge>gradlew -Dorg.gradle.java.home="C:/Pylo/MCreator183/jdk" -Dorg.gradle.parallel=false -Dorg.gradle.jvmargs="-Xms4095m -Xmx4095m" setupDecompWorkspace --refresh-dependencies 
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\MCreator183\forge>
Task completed with return code 0 in 2411 milliseconds

Jump to top