除了上面的答案，你还需要弄清楚为什么gradle进程退出而不释放锁来永久修复它。

在我的情况下，我做了所有*。锁定文件删除和Android Studio的无效缓存选项。但问题不断出现。

在终端中手动运行gradlew显示，当JVM堆空间耗尽时，gradle进程会过早退出。这个回答帮助解决了这个问题。

./gradlew build #to detect what crashes gradle processes
./gradlew --stop #to stop any running gradle processes

在解决问题后(例如:堆耗尽)

find .gradle/ -type f -name "*.lock" -delete #delete lock files
./gradlew build #Try building the project

只是杀死java.exe进程修复我的问题。

——编辑——

如果没有修复，则:

关闭OpenJdkPlatform进程。

如果没有修复，则:

删除所有”。(windows: c:\ users \用户名\.gradle)。

如果没有修复，则:

重命名或删除.gradle目录后重试。

在@Sean Stayns的回答中引用了一个场景，以防它能帮助到任何人:如果你把你的项目保存在谷歌Drive文件夹中——不要这样做。只需将项目移动到本地驱动器即可解决此问题。

In the case we were trying to solve, were were also getting the "It is currently in use by another Gradle instance" error and nothing we tried here worked. The process ID was unknown as well. It didn't immediately occur to me to ask where the project was being saved, so in case anyone new to Android Dev is saving their projects to a Google Drive folder, just move over to your local drive. I would have just left this as a comment in @Sean Stayns's answer, but I can't comment. Hopefully it benefits someone.

Windows用户:

Gradle失败消息后面通常跟着相关的进程id，所以应该是这样 Gradle同步失败:超时等待锁定守护进程地址注册表[…] 它目前正在被另一个Gradle实例使用。

Owner PID: 8080
Our PID: 89765
Owner Operation: ...
In order to unlock, just kill the owner process:

taskkill /PID 8080 /F
taskkill /PID 89765 /F

每个人最后, 我有完整的解决方案

Error :- Timeout Gradle cashe its running in other gradle


distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-4.6-all.zip
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists

Please add this Line in Wrapper.Propertis and Sync now
After Sync the project When 
Invalidthcast\restart   to get the requesting componants

只要删除你的。gradle文件夹在android文件夹

如果在您的文件资源管理器(WINDOWS)或查找器(MAC)中不可用

Windows操作系统: 转到查看选项并检查显示隐藏文件

对于Mac

只需按CMD + shift +。

现在运行你的应用程序。