ESET block Gradle after latest update

[EjEm 0]

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.

[itman 1,743]

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

[Jared 0]

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.

[Marcos 5,243]

Please report the issue to ESET via a support ticket.

[Jared 0]

Thanks Marcos, done Case #00808528

[EjEm 0]

@Jared do you also have this problem ? 

#00813268 my ticket. Thx 

[Jared 0]

@EjEm Yep, I suspect it's the same issue.

[EjEm 0]

New version of client fixed the issue. 8.1.6.0

[Machado 0]

My ticket id #4BM-3JX-4W9W

This issue is still observed in Apple Silicon chips.

 

[Jared 0]

No improvement for me after upgrading to 8.1.6.0, rolling back to v6 fixes the issue.

Edited Tuesday at 10:18 PM by Jared

[Machado 0]

We're also observing the same issue.

We're now seeing different outcomes on different platforms: Intel is now working in 8.1.6.0; Apple Silicon the issue persists.

 

I've opened a ticket with ESET support - ticket id #4BM-3JX-4W9W

 

Hope this helps.

[Jared 0]

I'm also on Apple Silicon, note when reproducing the issue you have to reboot after installing EES. The problem doesn't occur until after your first reboot.

[Machado 0]

We're getting unconsistent reports. At the moment the issue is verified in both INTEL and Apple Silicon.

Yesterday, we had a number of laptops running EES v8.1.6.0, both INTEL and Apple Silicon working without issues for a few hours, including after restart. By the end of the day, all stoped and not working, not intel, not apple silicon.

Looks like, that for now, we'll have to halt v8 and rollback to v6.

This means that we'll need to hold macOS 15 deployment.