Java jvm used by gradle ran out of available ram mcreator ошибка

**I tried creating a Spigot plugin. It says it can’t create new workspace. «Build failed».

I checked my MCReator version and updated Java. Still not working.

Anyone know why is that?**

I copied error to clipboard, here it is.

Executing
Gradle task: dependencies buildLatestSpigot —refresh-dependencies

Build
info: MCreator 2020.5.47520, spigot-1.16.4, 64-bit, 8026 MB, Windows 10,
JVM 1.8.0_265, JAVA_HOME: C:Program FilesPyloMCreatorjdk

Root
project

annotationProcessor
— Annotation processors and their dependencies for source set ‘main’.

No
dependencies

apiElements
— API elements for main. (n)

No
dependencies

archives
— Configuration for archive artifacts.

No
dependencies

compileClasspath
— Compile classpath for source set ‘main’.

—
org.spigotmc:spigot-api:1.16.4-R0.1-SNAPSHOT

    +--- commons-lang:commons-lang:2.6


    +--- com.google.guava:guava:21.0


    +--- com.google.code.gson:gson:2.8.0


    +--- net.md-5:bungeecord-chat:1.16-R0.3


    |    +--- com.google.code.gson:gson:2.8.0


    |    --- com.google.guava:guava:21.0


    --- org.yaml:snakeyaml:1.26

compileOnly
— Compile only dependencies for source set ‘main’. (n)

—
org.spigotmc:spigot-api:1.16.4-R0.1-SNAPSHOT (n)

default
— Configuration for default artifacts.

No
dependencies

implementation
— Implementation only dependencies for source set ‘main’. (n)

No
dependencies

runtimeClasspath
— Runtime classpath of source set ‘main’.

No
dependencies

runtimeElements
— Elements of runtime for main. (n)

No
dependencies

runtimeOnly
— Runtime only dependencies for source set ‘main’. (n)

No
dependencies

testAnnotationProcessor
— Annotation processors and their dependencies for source set ‘test’.

No
dependencies

testCompileClasspath
— Compile classpath for source set ‘test’.

No
dependencies

testCompileOnly
— Compile only dependencies for source set ‘test’. (n)

No
dependencies

testImplementation
— Implementation only dependencies for source set ‘test’. (n)

No
dependencies

testRuntimeClasspath
— Runtime classpath of source set ‘test’.

No
dependencies

testRuntimeOnly
— Runtime only dependencies for source set ‘test’. (n)

No
dependencies

(o)
— dependencies omitted (listed previously)

(n)
— Not resolved (configuration is not meant to be resolved)

A
web-based, searchable dependency report is available by adding the —scan
option.

Download
https://hub.spigotmc.org/jenkins/job/BuildTools/lastSuccessfulBuild/art…

Loading
BuildTools version: git-BuildTools-7fe9375-122 (#122)

Java
Version: Java 8

Current
Path: C:UsersKorisnikMCreatorWorkspacesresawsdbuildbtmp.

Could not find PortableGit installation, downloading. 

Starting
download of
https://static.spigotmc.org/git/PortableGit-2.24.1.2-64-bit.7z.exe

Downloaded
file: PortableGit-2.24.1.2-64-bitPortableGit-2.24.1.2-64-bit.7z.exe with
hash: cb75e4a557e01dd27b5af5eb59dfe28adcbad21638777dd686429dd905d13899

Extracting
downloaded git install

Exception
in thread «main» java.lang.RuntimeException: Error running command, return
status !=0: [cmd.exe, /D, /C,
C:UsersKorisnikMCreatorWorkspacesresawsdbuildbtmpPortableGit-2.24.1.2-64-bitPortableGit-2.24.1.2-64-bit.7z.exe,
-y, -gm2, -nr]

  at org.spigotmc.builder.Builder.runProcess0(

Builder.java:819

  at org.spigotmc.builder.Builder.runProcess0(Builder.java:819)


  at org.spigotmc.builder.Builder.runProcess(

Builder.java:756

  at org.spigotmc.builder.Builder.runProcess(Builder.java:756)


  at org.spigotmc.builder.Builder.main(

Builder.java:211

  at org.spigotmc.builder.Builder.main(Builder.java:211)


  at org.spigotmc.builder.Bootstrap.main(

Bootstrap.java:34

  at org.spigotmc.builder.Bootstrap.main(Bootstrap.java:34)

Task :buildLatestSpigot FAILED

FAILURE:
Build failed with an exception.

• Where:

Build
file ‘C:UsersMEMCreatorWorkspacesresawsdbuild.gradle’ line: 28

• What went wrong:

Execution
failed for task ‘:buildLatestSpigot’.

Process 'command 'C:Program FilesPyloMCreatorjdkbinjava.exe''
finished with non-zero exit value 1

• Try:

Run
with —stacktrace option to get the stack trace. Run with —info or
—debug option to get more log output. Run with —scan to get full
insights.

• Get more help at https://help.gradle.org

BUILD
FAILED in 1m 31s

2
actionable tasks: 2 executed

BUILD
FAILED

Task
completed in 92266 milliseconds

For some reason it says it stops gradle.

Setting up Gradle project files > Stopping running Gradle > Setting up Gradle project > and then it don’t do anything

Gradle is a build management tool for java and android projects.

Usually, javalangoutofmemoryerror comes running an android application for the following tasks.

• Building phase
• compile phase
• Package phase
• Loading app in Android studio
• Starting Android studio application

Did you get the below errors while compiling the android project?

• java.lang.OutOfMemoryError: Java heap space
• java.lang.OutOfMemoryError: Perm Gen space
• java.lang.OutOfMemoryError: GC overhead limit exceeded
• The system is out of resources

What is the reason for java.lang.OutOfMemoryError?
For example, if the project has a lot of java files say 1000 when you try to build the project using “gradle clean build”,
For a successful case,
gradle clean build will try to clean/delete the project and compile the project, test the project and build the application.

For the failure case, the build failed with an error because there is enough Heap memory to run large code.

The OutOfMemoryError error occurs when there is enough heap memory for your Gradle process to execute the android project

OutOfMemoryError issues occur either in the compile phase of your project or the test phase of your project while building your Gradle project.

For debugging it, First, find out which phase of your build is occurring

If the error occurs during compilation, you must increase heap size thus according to your system capacity and use the following lines of code in Linux and Windows.

There isn’t enough room in heap memory to allocate your object execution in Java.
When this problem occurs in Gradle, you must use the system classloader because the classloader loads the classes, but your application still maintains the references to the classes after execution is complete, which is referred to as a memory leak.

Solution for OutOfMemory Error in Gradle

There are many ways we can fix it

First way,
In the Application android/Gradle.properties, Try to add the below properties

android.useAndroidX=true
android.enableJetifier=true
org.gradle.daemon=true
org.gradle.configureondemand=true
org.gradle.jvmargs=-Xmx4g -XX:MaxPermSize=4096m -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8

android.useAndroidX and android.enableJetifier enables to migrate of all support libraries to AndroidX and android team changes are released in androidx, so you will always get the latest clean and performance code.
org.gradle.jvmargs contains heap memory configuration which you can increase based on your hardware RAM. Higher is always preferable.

org.Gradle.daemon is a background daemon thread that initializes and runs in the background to cache data, thus improving performance.

Second way,

android:{
  dexOption:{
    javaMaxHeapSize "4g"
  }
}

The third option, You can pass maxPermsize inside the Gradle task

compile{
  jvmArgs "-XX:MaxPermSize=1096m"
  freeCompilerArgs  ['-Xjsr305=strict', '-XXLanguage:-NewInference']
}

How to fix the OutofMemoryError error in android studio

sometimes, You used to get Out of memory errors When you are loading or starting a project in Android studio.

The application has no memory to run the process for loading in Android studio or project.
There are multiple ways to fix this error.

Approach 1:
You need to add the following attributes to the application tag in manifest.xml

android:hardwareAccelerated="false"
android:largeHeap="true"

After adding this code, Try to restart the application, Now your app has enough memory allocated to run the code in RAM.

Approach2:

You have to configure Gradle.properties with maxHeapSize properties as discussed above

Fix for OutOfMemoryError for gradle in windows:-

change the environment variable GRADLE_OPTS in such a way that increases the heap size by following a piece of code

GRADLE_OPTS="$GRADLE_OPTS  "-Xmx4096" "-Xms1024m" "-XX:MaxPermSize=4096""

Changed the maxPermSize values to 4096

Fix for OutOfMemoryError for gradle in Linux/Unix:-

In Linux and Unix machines, We have to incase the heap size for the environment variable GRADLE_OPTS.
the processing for the Linux version is different

export GRADLE_OPTS=-Xmx4096M -XX:MaxPermSize=7096M  

Most of the time OutOfMemoryError solves with the above lines of code.

Conclusion

In this tutorial, You learned different ways to solve OutOfMemoryError in Gradle build with the android app.