找不到可用的空闲守护进程 [英] Unable to find a usable idle daemon

查看:38
本文介绍了找不到可用的空闲守护进程的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在尝试在 Visual Studio Code 中使用 Talon SRX 和 WPILib for First Robotics for Java.我按照这里的说明操作:https://phoenix-documentation.readthedocs.io/en/latest/ch05a_CppJava.html.但是当我开始尝试构建测试的步骤时 - https://phoenix-documentation.readthedocs.io/en/latest/ch05a_CppJava.html#frc-java-build-test-single-talon - 我收到以下消息:

I am trying to use Talon SRX with WPILib for First Robotics for Java in Visual Studio Code. I follow the instructions here: https://phoenix-documentation.readthedocs.io/en/latest/ch05a_CppJava.html. But when I get to the step where I try the build test - https://phoenix-documentation.readthedocs.io/en/latest/ch05a_CppJava.html#frc-java-build-test-single-talon - I get the following message:

FAILURE:构建失败,出现异常.

FAILURE: Build failed with an exception.

  • 出了什么问题:无法找到可用的空闲守护进程.我已经连接到 100 个不同的守护进程,但我无法使用它们中的任何一个来运行构建.BuildActionParameters 是 DefaultBuildActionParameters{,currentDir=c:\Users\furch\OneDrive\Documents\TalonLibrary\Test\TestTesr,systemProperties size=59,envVariables size=59,logLevel=LIFECYCLE,useDaemon=true,continuous=false,injectedPluginClasspath=[]}.

  • What went wrong: Unable to find a usable idle daemon. I have connected to 100 different daemons but I could not use any of them to run the build. BuildActionParameters were DefaultBuildActionParameters{, currentDir=c:\Users\furch\OneDrive\Documents\TalonLibrairy\Test\TestTesr, systemProperties size=59, envVariables size=59, logLevel=LIFECYCLE, useDaemon=true, continuous=false, injectedPluginClasspath=[]}.

试试:使用 --stacktrace 选项运行以获取堆栈跟踪.使用 --info 或 --debug 选项运行以获得更多日志输出.使用 --scan 运行以获得完整的见解.

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.

https://help.gradle.org 获取更多帮助终端进程以退出代码终止:1

Get more help at https://help.gradle.org The terminal process terminated with exit code: 1

如果可以,请帮忙.

推荐答案

这个问题发生在使用第三方软件包时,他们分配了过多的系统内存,而您的机器不兼容.可能这就是背后的原因.

This problem is happening for using third party packages in which they allocated too much system memory with that your machine is not compatible. May be that's the reason behind it.

那么如何解决这个问题:

so how to resolve this issue :

  1. 转到gradle.properties 文件,你会发现类似org.gradle.jvmargs=-Xmx1536M
  2. 现在将其更改为 org.gradle.jvmargs=-Xmx1024M,在重新运行模拟器后将 1024 替换为 1536.希望这个问题能得到解决.
  1. go to gradle.properties file and you will find something like org.gradle.jvmargs=-Xmx1536M
  2. now change it to org.gradle.jvmargs=-Xmx1024M,replace 1024 in place of 1536 after that re-run your emulator. Hopefully this issue will be resolved.

这篇关于找不到可用的空闲守护进程的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆