守护进程在 JVM 垃圾收集器抖动和 JVM 内存耗尽后立即停止

2024-04-06

当我使用 gradle 6.0 构建多模块 java 项目时,当我添加 >30 个模块时。抛出此错误:

Gradle Daemon started in 2 s 267 ms

> Configure project :soa-misc
"/opt/dabai/tools/jdk1.8.0_211/jre/lib/ext/"
null
Expiring Daemon because JVM heap space is exhausted
Daemon will be stopped at the end of the build after running out of JVM memory
Expiring Daemon because JVM heap space is exhausted
Expiring Daemon because JVM heap space is exhausted
Expiring Daemon because JVM heap space is exhausted
Expiring Daemon because JVM heap space is exhausted
Expiring Daemon because JVM heap space is exhausted
Expiring Daemon because JVM heap space is exhausted
Expiring Daemon because JVM heap space is exhausted
Expiring Daemon because JVM heap space is exhausted
Expiring Daemon because JVM heap space is exhausted
Expiring Daemon because JVM heap space is exhausted
Expiring Daemon because JVM heap space is exhausted
Daemon is stopping immediately JVM garbage collector thrashing and after running out of JVM memory

我试图在我的中添加参数$HOME/.gradle/gradle.properties:

org.gradle.jvmargs=-Xmx8096m -XX:MaxPermSize=8096m -XX:+HeapDumpOnOutOfMemoryError

但问题并没有解决,我该怎么办?


I add gradle.properties文件在我的根项目目录中,并添加此配置:

org.gradle.jvmargs=-Xmx4096M

作品。从错误信息中我们可以知道Daemon JVM空间耗尽。这是摇篮官方文件 https://docs.gradle.org/current/userguide/build_environment.html关于这个配置:

指定用于 Gradle 守护程序的 JVM 参数。设置为 对于配置构建的 JVM 内存设置特别有用 表现。这不会影响 Gradle 的 JVM 设置 客户端虚拟机。默认为-Xmx512m“-XX:MaxMetaspaceSize=256m”。

本文内容由网友自发贡献,版权归原作者所有,本站不承担相应法律责任。如您发现有涉嫌抄袭侵权的内容,请联系:hwhale#tublm.com(使用前将#替换为@)

守护进程在 JVM 垃圾收集器抖动和 JVM 内存耗尽后立即停止 的相关文章

随机推荐