java exit 137,为什么我的Gradle会因退出代码137而死亡？

最新推荐文章于 2021-03-06 11:34:33 发布
最新推荐文章于 2021-03-06 11:34:33 发布
阅读量353 收藏
点赞数
文章标签： java exit 137
在尝试使用Gradle构建和测试大型项目时遇到问题，测试在执行过程中意外终止，疑似由内存不足引起。增加内存分配和调试级别后问题依然存在。堆栈跟踪显示进程以非零退出值137结束，可能是Linux内核的OOM杀手在虚拟内存紧张时强制终止进程。解决方案可能涉及检查Linux系统的内存管理和Gradle的内存配置。
摘要由CSDN通过智能技术生成

I've been trying to compile and test a large project to use Gradle. The test run fine until they die unexpectedly. I dug around and resources said that this is due to a memory issue. If I reduce the number of tests in the suite, it runs fine.

I increased the memory by 4x increased the debugging level but I still don't follow what causes this. Here's the horribly cryptic stacktrace. The last line (scroll right) shows the memory settings that I've defined.

...

...

...

1125 tests completed, 30 failed, 9 skipped

:test FAILED

:test (Thread[Daemon worker,5,main]) completed. Took 8 mins 39.684 secs.

FAILURE: Build failed with an exception.

* What went wrong:

Execution failed for task ':test'.

> Process 'Gradle Test Executor 1' finished with non-zero exit value 137

* Try:

Run with --debug option to get more log output.

* Exception is:

org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':test'.

at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:69)

at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:46)

at org.gradle.api.internal.tasks.execution.PostExecutionAnalysisTaskExecuter.execute(PostExecutionAnalysisTaskExecuter.java:35)

at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:64)

at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:58)

at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:52)

at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52)

at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:53)

at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)

at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:203)

at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:185)

at org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.processTask(AbstractTaskPlanExecutor.java:66)

at org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.run(AbstractTaskPlanExecutor.java:50)

at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor.process(DefaultTaskPlanExecutor.java:25)

at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter.execute(DefaultTaskGraphExecuter.java:110)

at org.gradle.execution.SelectedTaskExecutionAction.execute(SelectedTaskExecutionAction.java:37)

at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:37)

at org.gradle.execution.DefaultBuildExecuter.access$000(DefaultBuildExecuter.java:23)

at org.gradle.execution.DefaultBuildExecuter$1.proceed(DefaultBuildExecuter.java:43)

at org.gradle.execution.DryRunBuildExecutionAction.execute(DryRunBuildExecutionAction.java:32)

at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:37)

at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:30)

at org.gradle.initialization.DefaultGradleLauncher$4.run(DefaultGradleLauncher.java:154)

at org.gradle.internal.Factories$1.create(Factories.java:22)

at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:90)

at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:52)

at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:151)

at org.gradle.initialization.DefaultGradleLauncher.access$200(DefaultGradleLauncher.java:32)

at org.gradle.initialization.DefaultGradleLauncher$1.create(DefaultGradleLauncher.java:99)

at org.gradle.initialization.DefaultGradleLauncher$1.create(DefaultGradleLauncher.java:93)

at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:90)

at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:62)

at org.gradle.initialization.DefaultGradleLauncher.doBuild(DefaultGradleLauncher.java:93)

at org.gradle.initialization.DefaultGradleLauncher.run(DefaultGradleLauncher.java:82)

at org.gradle.launcher.exec.InProcessBuildActionExecuter$DefaultBuildController.run(InProcessBuildActionExecuter.java:94)

at org.gradle.tooling.internal.provider.ExecuteBuildActionRunner.run(ExecuteBuildActionRunner.java:28)

at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35)

at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:43)

at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:28)

at org.gradle.launcher.exec.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:78)

at org.gradle.launcher.exec.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:48)

at org.gradle.launcher.daemon.server.exec.ExecuteBuild.doBuild(ExecuteBuild.java:52)

at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)

at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)

at org.gradle.launcher.daemon.server.exec.WatchForDisconnection.execute(WatchForDisconnection.java:37)

at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)

at org.gradle.launcher.daemon.server.exec.ResetDeprecationLogger.execute(ResetDeprecationLogger.java:26)

at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)

at org.gradle.launcher.daemon.server.exec.RequestStopIfSingleUsedDaemon.execute(RequestStopIfSingleUsedDaemon.java:34)

at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)

at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.call(ForwardClientInput.java:74)

at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.call(ForwardClientInput.java:72)

at org.gradle.util.Swapper.swap(Swapper.java:38)

at org.gradle.launcher.daemon.server.exec.ForwardClientInput.execute(ForwardClientInput.java:72)

at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)

at org.gradle.launcher.daemon.server.health.DaemonHealthTracker.execute(DaemonHealthTracker.java:40)

at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)

at org.gradle.launcher.daemon.server.exec.LogToClient.doBuild(LogToClient.java:66)

at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)

at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)

at org.gradle.launcher.daemon.server.exec.EstablishBuildEnvironment.doBuild(EstablishBuildEnvironment.java:72)

at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)

at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)

at org.gradle.launcher.daemon.server.health.HintGCAfterBuild.execute(HintGCAfterBuild.java:41)

at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)

at org.gradle.launcher.daemon.server.exec.StartBuildOrRespondWithBusy$1.run(StartBuildOrRespondWithBusy.java:50)

BUILD FAILED at org.gradle.launcher.daemon.server.DaemonStateCoordinator$1.run(DaemonStateCoordinator.java:246)

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

at org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)

Caused by: org.gradle.process.internal.ExecException: Process 'Gradle Test Executor 1' finished with non-zero exit value 137

Total time: 9 mins 38.624 secs

at org.gradle.process.internal.DefaultExecHandle$ExecResultImpl.assertNormalExitValue(DefaultExecHandle.java:367)

at org.gradle.process.internal.DefaultWorkerProcess.waitForStop(DefaultWorkerProcess.java:161)

at org.gradle.api.internal.tasks.testing.worker.ForkingTestClassProcessor.stop(ForkingTestClassProcessor.java:86)

at org.gradle.api.internal.tasks.testing.processors.RestartEveryNTestClassProcessor.endBatch(RestartEveryNTestClassProcessor.java:60)

at org.gradle.api.internal.tasks.testing.processors.RestartEveryNTestClassProcessor.stop(RestartEveryNTestClassProcessor.java:54)

at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)

at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)

at org.gradle.messaging.dispatch.FailureHandlingDispatch.dispatch(FailureHandlingDispatch.java:29)

at org.gradle.messaging.dispatch.AsyncDispatch.dispatchMessages(AsyncDispatch.java:132)

at org.gradle.messaging.dispatch.AsyncDispatch.access$000(AsyncDispatch.java:33)

at org.gradle.messaging.dispatch.AsyncDispatch$1.run(AsyncDispatch.java:72)

... 2 more

Stopped 0 compiler daemon(s).

Received result Failure[value=org.gradle.initialization.ReportedException: org.gradle.internal.exceptions.LocationAwareException: Execution failed for task ':test'.] from daemon DaemonInfo{pid=48, address=[65adcc0f-8881-4511-b7a0-1b88c7016510 port:34390, addresses:[/0:0:0:0:0:0:0:1%lo, /127.0.0.1]], idle=false, context=DefaultDaemonContext[uid=14546872-57d6-4da6-8358-dc41cb7bb01d,javaHome=/usr/lib/jvm/java-8-oracle,daemonRegistryDir=/srv/myapplication/.gradle/daemon,pid=48,idleTimeout=120000,daemonOpts=-XX:MaxMetaspaceSize=320m,-XX:+DisableExplicitGC,-XX:+UseConcMarkSweepGC,-XX:NewSize=124m,-XX:SurvivorRatio=16,-Xms257m,-Xmx2049m,-Dfile.encoding=UTF-8,-Duser.country=US,-Duser.language=en,-Duser.variant]} (build should be done).

解决方案

This issue seems to be related to Linux rather than Gradle as stated in the Jenkins docs:

In cases where virtual memory is running short the kernel OOM (Out of

Memory) killer may forcibly kill Jenkins or individual builds. If this

occurs on Linux you may see builds terminate with exit code 137 (128 +

signal number for SIGKILL). The dmesg command output will show log

messages that will confirm the action that the kernel took.

Alin John
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
Gradle学习(七)——持续构建
独自登高楼 望断天涯路
12-25 3083
会指定要执行的任务让Gradle来执行。Gradle会分析你给出的任务需要执行的所有任务集合，按照顺序全部执行他们，然后停下来等你的下一次指令。持续集成则不同，它会按照你给出的任务指令，不断的分析构建结果是否过期，如果过期则会再次执行构建，除非你强制让它停下
IDEA 下载项目出现报错：svn process exited with error code 137
张小凡
07-31 9211
svn process exited with error code 137
Jenkins构建项目过程中：ERROR: Maven JVM terminated unexpectedly with exit code 137
weixin_43564627的博客
12-20 2409
ERROR: Maven JVM terminated unexpectedly with exit code 137 简单的来说就是内存溢出 2.解决 linux上 vi /etc/profile 添加： export MAVEN_OPTS="-Xms1024m -Xmx1024m -Xss1m" 意思就是扩充内存 最后别忘了，使用source命令使修改立刻生效： source /etc...
java exit 137_运维：k8s pod erro exit code 137
weixin_31699893的博客
03-06 381
The application hit an OOM (out of memory) condition. With regards to OOM condition handling, review the node's kernel logs to validate whether this occurred. This would require knowing which node the...
java exit code 137,解决Java结果137
weixin_36476970的博客
02-16 1573
I am running a java process on amazon ec2. It ran for 72 mins and then suddenly I get "java result 137". That is all, there are no exceptions or any other error messages. I have searched for this erro...
android studio 报错finished with non-zero exit value -1073741819
小龙五的博客
12-04 324
finished with non-zero exit value -1073741819 finished with non-zero exit value -1 (2,3) androidstudio报错 都是例如: buildToolsVersion = "22.0.1" 版本和主版本不一致导致的. 只需要修改成统一的版本的就可以了. 我们的项目是组件化开发的.所以有很...
github-actions-gradle
03-22
使用`run: echo "::set-output name=exit_code::${PIPESTATUS[0]}"`来记录退出状态码，方便后续分析。 7. **集成持续集成(CI)和持续部署(CD)** GitHub Actions 可以与各种服务集成，如Jenkins、Travis CI等，实现C...
【Gradle】【WSL】/home/linuxbrew/.linuxbrew/opt/openjdk/libexec/bin/java: Exec format error
DovSnier 专栏
09-18 773
目录 一. 问题 二. 安装 gradle 三. 问题追踪 3.1 思路 3.2 解决 3.3 分析参考 四. 参考 一. 问题 最近在WSL 中安装gradle 过程中，遇到如下问题: 即, /home/linuxbrew/.linuxbrew/Cellar/gradle/6.6.1/libexec/bin/gradle: 185: exec: /home/linuxbrew/.linuxbrew/opt/openjdk/libexec/bin/java: Ex...
Android Studio编译问题：ProcessException: org.gradle.process.internal.ExecException
u012310391的专栏
06-05 3316
问题: ：Error:Execution failed for task ‘:BuildingQM:transformClassesWithDexForProdHouseqm_debug’. com.android.build.api.transform.TransformException: com.android.ide.common.process.ProcessException:
开发中碰到的问题：org.gradle.process.internal.ExecException: Process 'command 'C:\Program Files\Java\jdk1.7.0
热门推荐
苦涩的风的博客
11-17 3万+
在用as开发项目的过程中，我碰到了这个错误，在网上找到了如下的解决方法，实测有效 被编译的代码或资源有问题（ finished with non-zero exit value 1）： 出现这种编译异常表现是exit value 1，一般会给出错误提示，所以很容易排查。这种错误很常见，错误提示有时候是在日志中明显的给出来了，如下示例所示： 123456
gradleb编译的finished with non-zero exit value问题
Lenny的专栏
06-29 2357
转载自：http://www.jacpy.com/2016/04/22/android-studio-error-collection.html 在使用Android studio过程中，使用gradle编译的时候总会出现一些问题，下面是几个常见问题的解决方法。 被编译的代码或资源有问题（ finished with non-zero exit value 1）： 出现这
关于finished with non-zero exit value 1、2、3的bug解决总结
bobge的IT专栏
03-28 1万+
在最近的一个项目中碰到好几次finished with non-zero exit value 1、finished with non-zero exit value 2、finished with non-zero exit value 3这种莫名其妙的bug导致程序编译不过去。现在闲下来了总结一下解决办法： finished with non-zero exit value 2：出现这种bu
command terminated with exit code 137
yiluoseraph的技术博客
11-06 6718
调整pod/docker的内存
Process finished with exit code 137 (interrupted by signal 9: SIGKILL)
OneQuestionADay的博客
01-04 7878
今天兴高采烈来到实验室跑代码，用tensorflow框架，跑着跑着突然发现被kill. 抛出以下提示： Process finished with exit code 137 (interrupted by signal 9: SIGKILL) 第一反应是GPU不够用了。查看下GPU，发现利用率50%都还不到。 没有想到的是，输入top查看CPU，发现是CPU爆了。 把batchsize从20改为4， ...
finished with non-zero exit value 3,gradle编译异常小结
抽烟的青蛙的专栏
06-16 7934
转载自：http://www.jacpy.com/2016/04/22/android-studio-error-collection.html 在使用android studio过程中，使用gradle编译的时候总会出现一些问题，下面是几个常见问题的解决方法。 被编译的代码或资源有问题（ finished with non-zero exit value 1）：出现这种编译异常表现是 exit
出现"xxxx finished with non-zero exit value 1"的原因和解决方法
神的孩子的博客
09-03 1万+
原因： 1、依赖重复了 2、v4、v7包与compileVersion版本不一致 3、缺少资源文件 解决： 修改v4包、v7包到与compileVersion一致； 终端执行： gradlew processDebugResources --debug 查看输出的log信息 ...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值