Ran out of allocated ram

Started by kitghost on

Topic category: Troubleshooting, bugs, and solutions

Joined May 2021
Points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • MCreator plugins:
  • Comments:
Ran out of allocated ram
Mon, 05/17/2021 - 08:05 (edited)

Installed Mcreator, tried to make my first workspace and let it run in the background then got told there was an error, it suggested just restarting the process if it was the first time so i did. Then it happened agian but this time with the message somthing along the lines of "ran out of ram" this is strange as I have 32gb of ram but I read on the forums that reinstalling could help so I did that, same thing agian. however this time i watched it in task manager and witnessed as it created more and more "openjdk platform binary" processes each using up about 170mb of ram *over and over and over* until it had used up all of my ram then it failed and said I ran out of ram. I cannot conceive why it would do this and since ive closed the program all of the processes stayed open and since i have about 50 of them at this point im having to manually close them. Im going to try anything I can find including running in admin incase its a problem of permission but holy cow is this ever annoying. Any help is appreciated!

 

https://imgur.com/a/3NNJpJr

(the aftermath, note that the program is no longer open not even under the hidden icon menu)

 

Edit1: I tried running in administrator to no avail, I do not have any windows security or firewall enabled because I am used to this sort of problem with them. I also frequently stream without problem so i find it hard to believe that my internet would be the problem but am willing to try anything at this point. Going to try deleting the /.mcreator/gradle folder next, skipping the delete caches folder step because there is no caches folder. I am currently watching it all happen agian as this program uses more ram :'-(

 

Executing 
    Gradle task: eclipse

Build 
    info: MCreator 2021.1.18117, forge-1.16.5, 64-bit, 32715 MB, Windows 10, 
    JVM 1.8.0_275, JAVA_HOME: C:\Program Files\Pylo\MCreator\jdk

org.gradle.tooling.GradleConnectionException: 
    Could not execute build using connection to Gradle distribution 
    'https://services.gradle.org/distributions/gradle-6.8.1-all.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$1$1.run(
DefaultAsyncConsumerActionExecutor.java:69
)

 
      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 Manual chapter on the daemon at 
    https://docs.gradle.org/6.8.1/userguide/gradle_daemon.html

Process 
    command line: C:\Program Files\Pylo\MCreator\jdk\bin\java.exe -Xms625m 
    -Xmx8192m -Dfile.encoding=windows-1252 -Duser.country=US 
    -Duser.language=en -Duser.variant -cp 
    C:\Users\User\.mcreator\gradle\wrapper\dists\gradle-6.8.1-all\923to48kq3drqywuppfjkcokx\gradle-6.8.1\lib\gradle-launcher-6.8.1.jar 
    org.gradle.launcher.daemon.bootstrap.GradleDaemon 6.8.1

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:38
)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

 
      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:144
)

 
      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$1$1.run(
DefaultAsyncConsumerActionExecutor.java:67
)

 
      ... 6 more

TASK 
    EXECUTION FAILED

Task 
    completed in 14 seconds

Edited by kitghost on Mon, 05/17/2021 - 08:05
Joined May 2021
Points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • MCreator plugins:
  • Comments:
Also worth noting I am using…
Mon, 05/17/2021 - 07:51

Also worth noting I am using the 64bit version of the program and have a 64 bit operating system if that wasnt already implied by  the 32gigs of ram lol