gradlew setupDecompWorkspace Error

[Torchit671]

I am new to Forge and I am attempting to set it up in order to start creating mods. However, I encountered an error that told me it could not reserve enough space for an object heap, as well as something concerning daemon.

• Solutions I've tried:
  • I found that this may be related to ram, so I attempted boosting my ram with a thumbdrive to no success.
  • Editing the gradle.properties file
  • Deleting everything and creating it again.

I was ready to give up, but then I found out that forge for 1.7.2 was working just fine using the same steps, and that I could probably make 1.7.2 mods. 

I am bewildered and in dire need of help. Thank you for your time.

 

Here is what I got from stacktrace:

  Reveal hidden contents

C:\Users\Chase\Documents\YoutubeWorkspace\Forgespace>gradlew setupDecompWorkspac
e --stacktrace
To honour the JVM settings for this build a new JVM will be forked. Please consi
der using the daemon: https://docs.gradle.org/2.14/userguide/gradle_daemon.html.

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:
-----------------------
Error occurred during initialization of VM
Could not reserve enough space for 3145728KB object heap

* 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:
-----------------------
Error occurred during initialization of VM
Could not reserve enough space for 3145728KB object heap

        at org.gradle.launcher.daemon.bootstrap.DaemonGreeter.parseDaemonOutput(
DaemonGreeter.java:34)
        at org.gradle.launcher.daemon.client.DefaultDaemonStarter.startProcess(D
efaultDaemonStarter.java:153)
        at org.gradle.launcher.daemon.client.DefaultDaemonStarter.startDaemon(De
faultDaemonStarter.java:136)
        at org.gradle.launcher.daemon.client.DefaultDaemonConnector.startDaemon(
DefaultDaemonConnector.java:111)
        at org.gradle.launcher.daemon.client.SingleUseDaemonClient.execute(Singl
eUseDaemonClient.java:52)
        at org.gradle.launcher.daemon.client.SingleUseDaemonClient.execute(Singl
eUseDaemonClient.java:37)
        at org.gradle.launcher.cli.RunBuildAction.run(RunBuildAction.java:43)
        at org.gradle.internal.Actions$RunnableActionAdapter.execute(Actions.jav
a: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(JavaRunti
meValidationAction.java:35)
        at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRunti
meValidationAction.java:24)
        at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionRep
ortingAction.java:33)
        at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionRep
ortingAction.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(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBoots
trap.java:55)
        at org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.j
ava:36)
        at org.gradle.launcher.GradleMain.main(GradleMain.java:23)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.gradle.wrapper.BootstrapMainStarter.start(BootstrapMainStarter.ja
va:30)
        at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:127)
        at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:61)

 

[Ele20002]

For some reason, it only worked for me when I tried in a new folder, but you have a different error, so it may not work for you

What IDE are you using - there's an alternative method if you're using IntelliJ

[Torchit671]

Thank you for your input, I am using eclipse

[Draco18s]

To me it looks like you need to allocate more RAM to the decompile process or you may need more RAM in your machine. (it looks like it gave up after trying to allocate more than ~3GB).

 

You can also try telling it to use less RAM (in the event that you don't have 3GB available in your machine and can't add any: e.g. a 32 bit OS).

Edited April 3, 2017 by Draco18s

[Torchit671]

Thank you very much for your help! I changed gradle.properties and the problem has been resolved. I still get an error when decompiling Mc, but I'm sure I just need to upgrade to Windows 64 bit to unlock my potential ram. 

[Draco18s]

Yeah, setting up on a 32 bit OS is dicey at best.

I managed it once having to continuously tweak the ram allocation up and down by increments until it worked (there's two different errors: one says it couldn't allocate the RAM, and you go down in MB, the other said it ran out of heap and you go up in MB).