EjEm 0 Posted August 8 Share Posted August 8 ESET kills a gradle daemon. I try some workarounds which didn't work, pause protection, lower engine sensitivity, put app to exclude mode. Only way to get it worked, is to disable eset completely from the system point of view. Quote Link to comment Share on other sites More sharing options...
itman 1,741 Posted August 8 Share Posted August 8 (edited) Here's the write-up on Gradle Daemon: https://docs.gradle.org/current/userguide/gradle_daemon.html . Quote Gradle runs on the Java Virtual Machine (JVM) and uses several supporting libraries with non-trivial initialization time. Startups can be slow. The Gradle Daemon solves this problem. The Gradle Daemon is a long-lived background process that reduces the time it takes to run a build. Have you tried an Eset Detection exclusion? Edited August 8 by itman Quote Link to comment Share on other sites More sharing options...
Jared 0 Posted August 22 Share Posted August 22 I get the same issue, I tried to do a log collection but it just seems to hang for 20 mins trying to collect the logs before I gave up. To reproduce: * Install ESET Endpoint Security v8 for OSX * Make sure you reboot otherwise it doesn't happen * Install gradle ( brew install gradle ) https://gradle.org/install/ * Run gradle --daemon You will receive the following error: gradle --daemon Welcome to Gradle 8.10! Here are the highlights of this release: - Support for Java 23 - Faster configuration cache - Better configuration cache reports For more details see https://docs.gradle.org/8.10/release-notes.html Starting a Gradle Daemon (subsequent builds will be faster) FAILURE: Build failed with an exception. * What went wrong: Could not dispatch a message to the daemon. * 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. > Get more help at https://help.gradle.org. The only way to get gradle working again is to uninstall ESET completely, disabling functionality in the app doesn't help. I do get a bunch of warnings in the system log from com.eset.filrewall: Could not find app info, return the original flow without filling in app info It's not clear if they're related. Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 5,234 Posted August 22 Administrators Share Posted August 22 Please report the issue to ESET via a support ticket. Quote Link to comment Share on other sites More sharing options...
Jared 0 Posted August 22 Share Posted August 22 Thanks Marcos, done Case #00808528 Quote Link to comment Share on other sites More sharing options...
EjEm 0 Posted September 2 Author Share Posted September 2 @Jared do you also have this problem ? #00813268 my ticket. Thx Quote Link to comment Share on other sites More sharing options...
Jared 0 Posted September 2 Share Posted September 2 @EjEm Yep, I suspect it's the same issue. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.