Android Studio：无法启动守护进程
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/20471311/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
Android Studio: Unable to start the daemon process
提问by buggydroid
I'm facing the below error when I'm trying to import a gradle project in Android Studio.
当我尝试在 Android Studio 中导入 gradle 项目时遇到以下错误。
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 guide chapter on the daemon at http://gradle.org/docs/1.8/userguide/gradle_daemon.html
Please read below process output to find out more:
and this is the output I see:
这是我看到的输出：
18:25:42.484 [main] DEBUG o.g.l.daemon.bootstrap.DaemonMain - Assuming the daemon was started with following jvm opts: [-XX:MaxPermSize=256m, -XX:+HeapDumpOnOutOfMemoryError, -Xmx1024m, -Dfile.encoding=windows-1252]
18:25:43.254 [main] DEBUG o.g.l.daemon.server.DaemonServices - Creating daemon context with opts: [-XX:MaxPermSize=256m, -XX:+HeapDumpOnOutOfMemoryError, -Xmx1024m, -Dfile.encoding=windows-1252]
18:25:43.306 [DEBUG] [org.gradle.logging.internal.DefaultLoggingConfigurer] Finished configuring with level: DEBUG, configurers: [org.gradle.logging.internal.OutputEventRenderer@47078ad, org.gradle.logging.internal.logback.LogbackLoggingConfigurer@7402a821, org.gradle.logging.internal.JavaUtilLoggingConfigurer@5a6c4a07]
18:25:43.356 [INFO] [org.gradle.launcher.daemon.server.Daemon] start() called on daemon - DefaultDaemonContext[uid=e58252c1-7a49-4be4-a6cd-1bd3d6d0880d,javaHome=C:\Program Files\Java\jdk1.7.0_45,daemonRegistryDir=C:\Users\Sowmya\.gradle\daemon,pid=15432,idleTimeout=60000,daemonOpts=-XX:MaxPermSize=256m,-XX:+HeapDumpOnOutOfMemoryError,-Xmx1024m,-Dfile.encoding=windows-1252]
18:25:43.362 [DEBUG] [org.gradle.launcher.daemon.server.DaemonStateCoordinator] updating lastActivityAt to 1386593743362
18:25:43.702 [DEBUG] [org.gradle.messaging.remote.internal.inet.InetAddressFactory] Adding IP addresses for network interface lo
18:25:43.705 [DEBUG] [org.gradle.messaging.remote.internal.inet.InetAddressFactory] Is this a loopback interface? true
18:25:43.706 [DEBUG] [org.gradle.messaging.remote.internal.inet.InetAddressFactory] Adding loopback address /127.0.0.1
18:25:43.707 [DEBUG] [org.gradle.messaging.remote.internal.inet.InetAddressFactory] Adding loopback address /0:0:0:0:0:0:0:1
18:25:43.708 [DEBUG] [org.gradle.messaging.remote.internal.inet.InetAddressFactory] Adding IP addresses for network interface net0
18:25:43.711 [DEBUG] [org.gradle.messaging.remote.internal.inet.InetAddressFactory] Is this a loopback interface? false
DefaultDaemonContext[uid=e58252c1-7a49-4be4-a6cd-1bd3d6d0880d,javaHome=C:\Program Files\Java\jdk1.7.0_45,daemonRegistryDir=C:\Users\Sowmya\.gradle\daemon,pid=15432,idleTimeout=60000,daemonOpts=-XX:MaxPermSize=256m,-XX:+HeapDumpOnOutOfMemoryError,-Xmx1024m,-Dfile.encoding=windows-1252]
18:25:43.951 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire exclusive lock on daemon addresses registry.
18:25:43.954 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired.
18:25:43.957 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
18:25:43.962 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire exclusive lock on daemon addresses registry.
18:25:43.963 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired.
18:25:43.966 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
18:25:43.976 [ERROR] [system.err]
18:25:43.977 [ERROR] [system.err] FAILURE: Build failed with an exception.
18:25:43.977 [ERROR] [system.err]
18:25:43.978 [ERROR] [system.err] * What went wrong:
18:25:43.979 [ERROR] [system.err] Could not write cache value to 'C:\Users\Sowmya\.gradle\daemon.8\registry.bin'.
18:25:43.979 [ERROR] [system.err]
18:25:43.980 [ERROR] [system.err] * Try:
18:25:43.981 [ERROR] [system.err] Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
18:25:44.009 [INFO] [org.gradle.launcher.daemon.bootstrap.DaemonMain] Daemon[pid = 15432] process has finished.
18:25:44.010 [DEBUG] [org.gradle.launcher.daemon.registry.PersistentDaemonRegistry] Removing daemon address: [9ae053cd-4dc2-4cb8-8f60-bb3c5983eb67 port:55117, addresses:[/127.0.0.1, /0:0:0:0:0:0:0:1]]
18:25:44.011 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire exclusive lock on daemon addresses registry.
18:25:44.012 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired.
18:25:44.013 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
18:25:44.014 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire exclusive lock on daemon addresses registry.
18:25:44.015 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired.
18:25:44.016 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
18:25:44.021 [DEBUG] [org.gradle.launcher.daemon.server.Daemon] VM shutdown hook was unable to remove the daemon address from the registry. It will be cleaned up later.
org.gradle.api.GradleException: Could not write cache value to 'C:\Users\Sowmya\.gradle\daemon.8\registry.bin'.
at org.gradle.cache.internal.SimpleStateCache.serialize(SimpleStateCache.java:74)
at org.gradle.cache.internal.SimpleStateCache.access0(SimpleStateCache.java:28)
at org.gradle.cache.internal.SimpleStateCache.run(SimpleStateCache.java:50)
at org.gradle.cache.internal.DefaultFileLockManager$DefaultFileLock.doWriteAction(DefaultFileLockManager.java:198)
at org.gradle.cache.internal.DefaultFileLockManager$DefaultFileLock.writeFile(DefaultFileLockManager.java:187)
at org.gradle.cache.internal.OnDemandFileAccess.writeFile(OnDemandFileAccess.java:58)
at org.gradle.cache.internal.SimpleStateCache.set(SimpleStateCache.java:48)
at org.gradle.cache.internal.FileIntegrityViolationSuppressingPersistentStateCacheDecorator.set(FileIntegrityViolationSuppressingPersistentStateCacheDecorator.java:38)
at org.gradle.cache.internal.FileIntegrityViolationSuppressingPersistentStateCacheDecorator.update(FileIntegrityViolationSuppressingPersistentStateCacheDecorator.java:46)
at org.gradle.launcher.daemon.registry.PersistentDaemonRegistry.remove(PersistentDaemonRegistry.java:109)
at org.gradle.launcher.daemon.server.Daemon.run(Daemon.java:100)
Caused by: java.io.FileNotFoundException: C:\Users\Sowmya\.gradle\daemon.8\registry.bin (Access is denied)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:221)
at java.io.FileOutputStream.<init>(FileOutputStream.java:171)
at org.gradle.cache.internal.SimpleStateCache.serialize(SimpleStateCache.java:67)
... 10 more`
I've turned off my anti-virus which was mentioned in a solution in SO. But nothing seems to work.
我已经关闭了在 SO 中的解决方案中提到的防病毒软件。但似乎没有任何效果。
回答by Scott Barta
Try deleting your .gradlefrom C:\Users\<username>directory and try again.
尝试从目录中删除您的.gradle 并重C:\Users\<username>试。
回答by Kunwar Avanish
1.If You just open too much applications in Windows and make the Gradle have no enough memory in Ram to start the daemon process.So when you come across with this situation,you can just close some applications such as iTunes and so on. Then restart your android studio.
1.如果你只是在Windows中打开了太多的应用程序，导致Gradle在Ram中没有足够的内存来启动守护进程，那么当你遇到这种情况时，你可以关闭一些应用程序，例如iTunes等。然后重启你的安卓工作室。
2.File Menu - > Invalidate Caches/ Restart->Invalidate and Restart.
2.文件菜单->无效缓存/重启->无效并重启。
回答by jrhamza
I also had same kind of issue. But managed to solve by Invalidate Cash.
我也有同样的问题。但设法通过无效现金解决。
From File Menu - > Invalidate Caches/ Restart..
从文件菜单 - > 无效缓存/重新启动..
It solved the problem for me.
它为我解决了这个问题。
回答by user2297930
In Eclipse, go to windows -> preferences -> gradle->arguments. Find JVM Arguments choose from radio button "USE :" and write arguments -Xms128m -Xmx512m Then click button Apply
在 Eclipse 中，转到 windows -> 首选项 -> gradle->arguments。查找 JVM Arguments 从单选按钮“USE :”中选择并写入参数 -Xms128m -Xmx512m 然后单击按钮 Apply
回答by Dinesh Vaitage
Try this... I have tried and work fine for me
试试这个......我已经尝试过并且对我来说工作正常
This issue is related to low memory...
此问题与内存不足有关...
Close your browsers, visual Studio and other services..
关闭您的浏览器、visual Studio 和其他服务。
after that run following command
之后运行以下命令
ionic build android
it will run successfully..
它会成功运行..
//Solutions is
create "gradle.properties" file in android folder and add following line into file
org.gradle.jvmargs=-Xmx512m -XX:MaxPermSize=512m
<your project>\platforms\android\gradle.properties
You can open browser and others..
您可以打开浏览器和其他..
ionic build android
Now it will work fine.
现在它会正常工作。
回答by Sosoel
Check your project folder. You may have there a file called gradle.properties and in there, check to see if you don't have this line:
检查您的项目文件夹。你可能有一个名为 gradle.properties 的文件，在那里，检查你是否没有这一行：
org.gradle.jvmargs=-Xmx2048m -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8
org.gradle.jvmargs=-Xmx2048m -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8
In my case, I just deleted the file, but check the contents to see if you don't actually want to keep some of the settings.
就我而言，我只是删除了该文件，但请检查内容以查看您是否真的不想保留某些设置。
回答by Saurabh
I faced this issue in intellij idea and solved by doing this,
我在intellij的想法中遇到了这个问题并通过这样做解决了，
try to set "VM options" to -Xmx512m at Settings | Build, Execution, Deployment | Build Tools | Gradle | Gradle VM options
尝试在 Settings | 中将“VM options”设置为 -Xmx512m 构建、执行、部署 | 构建工具 | 摇篮 | Gradle 虚拟机选项
回答by penkzhou
Sometimes You just open too much applications in Windows and make the gradle have no enough memory to start the daemon process.So when you come across with this situation,you can just close some applications such as Chrome and so on. Then restart your android studio.
有时候你只是在 Windows 中打开了太多的应用程序，导致 gradle 没有足够的内存来启动守护进程。所以当你遇到这种情况时，你可以关闭一些应用程序，例如 Chrome 等。然后重启你的安卓工作室。
回答by bolski
For me, in our work environment, we have Windows 7 64-bit with the machines locked down running McAfee with Host Intrusion turned on.
对我来说，在我们的工作环境中，我们有 Windows 7 64 位，机器被锁定，运行 McAfee，主机入侵打开。
I turned off Host Intrusion and gradle would finally work, so definitely, it appears to be issues with certain Virus scanners.
我关闭了主机入侵，gradle 终于可以工作了，所以肯定的是，这似乎是某些病毒扫描程序的问题。
UPDATE: Well I spoke too soon. Yes, I know longer get the "Unable to start the daemon process" message, but now I get the following:
更新：嗯，我说得太早了。是的，我知道不再收到“无法启动守护进程”消息，但现在我得到以下信息：
Error:Could not list versions using M2 pattern 'http://jcenter.bintray.com/[organisation]/[module]/[revision]/[artifact]-revision.[ext]'.
错误：无法使用 M2 模式“ http://jcenter.bintray.com/[organisation]/[module]/[revision]/[artifact]-revision.[ext]”列出版本。
回答by Jasongiss
I was getting this same issue, and none of the other answers here helped my particular case.
我遇到了同样的问题，这里的其他答案都没有帮助我的特殊情况。
It turned out to be because my Android Studio project was defaulting to use JDK 8.
原来是因为我的 Android Studio 项目默认使用 JDK 8。
Changing this, in the project settings, to point at a JDK 7 installation fixed this for me.
在项目设置中将其更改为指向 JDK 7 安装为我修复了此问题。
