Java JVM Ran Out Of Allocated Ram (please read before closing)

Started by superProxi64 on

Topic category: Troubleshooting, bugs, and solutions

Last seen on 16:11, 8. Jun 2022
Joined May 2019
Points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • MCreator plugins:
  • Comments:
Java JVM Ran Out Of Allocated Ram (please read before closing)

Computer broke, got it reset, and I'm attempting to redownload MCreator. I download it, start a new workspace, and I'm told that I didn't allocate enough RAM. I went to my preferences and allocated the max MCreator can take from my computer (4,096MB binary/4GB) and I get the same error. I've tried everything on the Gradle setup errors knowledge base and absolutely nothing worked. And yes, I did see the thread on preferences to change my allocated RAM, which is what I did in the beginning and it didn't work. Here is the error log:
 

Executing Gradle task: eclipse

Build info: MCreator 2020.2.14217, 1.14.4, 64-bit, 8059 MB, Windows 10, JVM 1.8.0_232, JAVA_HOME: C:\Program Files\Pylo\MCreator\jdk

org.gradle.tooling.GradleConnectionException: Could not execute build using Gradle distribution 'https://services.gradle.org/distributions/gradle-4.9-bin.zip'.

   at org.gradle.tooling.internal.consumer.ExceptionTransformer.transform(ExceptionTransformer.java:55)

   at org.gradle.tooling.internal.consumer.ExceptionTransformer.transform(ExceptionTransformer.java:29)

   at org.gradle.tooling.internal.consumer.ResultHandlerAdapter.onFailure(ResultHandlerAdapter.java:43)

   at org.gradle.tooling.internal.consumer.async.DefaultAsyncConsumerActionExecutor.lambda$run$0(DefaultAsyncConsumerActionExecutor.java:57)

   at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)

   at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)

   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

   at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56)

   at java.lang.Thread.run(Thread.java:748)

Caused by: 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/4.9/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

   at org.gradle.launcher.daemon.client.DaemonGreeter.parseDaemonOutput(DaemonGreeter.java:35)

   at org.gradle.launcher.daemon.client.DefaultDaemonStarter.startProcess(DefaultDaemonStarter.java:160)

   at org.gradle.launcher.daemon.client.DefaultDaemonStarter.startDaemon(DefaultDaemonStarter.java:136)

   at org.gradle.launcher.daemon.client.DefaultDaemonConnector.doStartDaemon(DefaultDaemonConnector.java:212)

   at org.gradle.launcher.daemon.client.DefaultDaemonConnector.startDaemon(DefaultDaemonConnector.java:206)

   at org.gradle.launcher.daemon.client.DefaultDaemonConnector.connect(DefaultDaemonConnector.java:130)

   at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:139)

   at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:93)

   at org.gradle.tooling.internal.provider.DaemonBuildActionExecuter.execute(DaemonBuildActionExecuter.java:60)

   at org.gradle.tooling.internal.provider.DaemonBuildActionExecuter.execute(DaemonBuildActionExecuter.java:41)

   at org.gradle.tooling.internal.provider.LoggingBridgingBuildActionExecuter.execute(LoggingBridgingBuildActionExecuter.java:58)

   at org.gradle.tooling.internal.provider.LoggingBridgingBuildActionExecuter.execute(LoggingBridgingBuildActionExecuter.java:37)

   at org.gradle.tooling.internal.provider.ProviderConnection.run(ProviderConnection.java:180)

   at org.gradle.tooling.internal.provider.ProviderConnection.run(ProviderConnection.java:124)

   at org.gradle.tooling.internal.provider.DefaultConnection.getModel(DefaultConnection.java:208)

   at org.gradle.tooling.internal.consumer.connection.CancellableModelBuilderBackedModelProducer.produceModel(CancellableModelBuilderBackedModelProducer.java:54)

   at org.gradle.tooling.internal.consumer.connection.PluginClasspathInjectionSupportedCheckModelProducer.produceModel(PluginClasspathInjectionSupportedCheckModelProducer.java:38)

   at org.gradle.tooling.internal.consumer.connection.AbstractConsumerConnection.run(AbstractConsumerConnection.java:64)

   at org.gradle.tooling.internal.consumer.connection.ParameterValidatingConsumerConnection.run(ParameterValidatingConsumerConnection.java:49)

   at org.gradle.tooling.internal.consumer.DefaultBuildLauncher$1.run(DefaultBuildLauncher.java:97)

   at org.gradle.tooling.internal.consumer.DefaultBuildLauncher$1.run(DefaultBuildLauncher.java:89)

   at org.gradle.tooling.internal.consumer.connection.LazyConsumerActionExecutor.run(LazyConsumerActionExecutor.java:87)

   at org.gradle.tooling.internal.consumer.connection.CancellableConsumerActionExecutor.run(CancellableConsumerActionExecutor.java:45)

   at org.gradle.tooling.internal.consumer.connection.ProgressLoggingConsumerActionExecutor.run(ProgressLoggingConsumerActionExecutor.java:61)

   at org.gradle.tooling.internal.consumer.connection.RethrowingErrorsConsumerActionExecutor.run(RethrowingErrorsConsumerActionExecutor.java:38)

   at org.gradle.tooling.internal.consumer.async.DefaultAsyncConsumerActionExecutor.lambda$run$0(DefaultAsyncConsumerActionExecutor.java:55)

   ... 6 more

TASK EXECUTION FAILED

Task completed in 15093 milliseconds

You have 8GB set the amount…
Thu, 04/02/2020 - 06:38

You have 8GB set the amount to say 6GB for the time of setup, then reduce it after the initial setup is done.

Last seen on 16:11, 8. Jun 2022
Joined May 2019
Points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • MCreator plugins:
  • Comments:
Nvm. Reinstalling worked for…
Fri, 04/03/2020 - 02:29

Nvm. Reinstalling worked for me. Thanks for the future advice, though!

Last seen on 11:23, 10. Oct 2022
Joined Apr 2021
Points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • MCreator plugins:
  • Comments:
i have the same problem but…
Tue, 04/27/2021 - 06:58

i have the same problem but for me it isnt working to reinstall?

 

Last seen on 18:20, 15. May 2023
Joined Feb 2021
Points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • MCreator plugins:
  • Comments:
Having same issue...
Wed, 05/19/2021 - 17:49

Having same issue...

Last seen on 20:37, 15. Mar 2022
Joined Mar 2022
Points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • MCreator plugins:
  • Comments:
RobuxTRex Hey, I just had…
Tue, 03/15/2022 - 20:06

RobuxTRex

Hey, I just had the same problem and the fix is really easy.
step 1 open setting and go to the system
step 2 go to about 
step 3 on the right side you will look after "advanced system settings" click it
step 4 above the "Ok-Cancel-Apply" you can see "environment Variables" Click it
Step 5 in the box where it says "system variables" You will find "_JAVA_OPTIONS" Click it and press edit Under the "system variables" Box
Step 6 change the numbers from 256 or anything lower than 300 and change it to something higher than 300 because that's what Mcreator has as default
Step 7 Click Apply and Ok on all the boxes

And you're done
:D