Keyboard lag with Messages and WhatsApp on Mac

[sudsandsoda 1]

Hi, 

 

With real time file system protection enabled, there is severe keyboard input lag with Messages, and WhatsApp.

 

Turning off RTFPS fixed this immediately. 

 

Any solutions?

[sudsandsoda 1]

To add... Adding WhatsApp / Messages to the exclusion list does not help.
Turning off "Scan on" / File Open does fix the issue. Leaving File Creation turned on is fine. 

Sequoia 15.1 (was fine on 15.0)

Edited November 1 by sudsandsoda

[Marcos 5,468]

This has been reported in a ticket for developers in the mean time.

Please collect logs as per the instructions at https://support.eset.com/en/kb3404, open a ticket with your local ESET distributor and supply them with the generated archive.

P_EECSM-6116

[VBpai 0]

I have the same issue with ESET Endpoint Security. All Macs that have ESETES deployed are experiencing severe lag in WhatsApp desktop client to a point where it's barely usable. Any tips will be greatly appreciated.

[kDash 0]

I have the exact same issue with iMessage, since upgraded to macOS 15.1, with ESET Endpoint Security v8.1.6.0.

It was fine with macOS 15.0

I don't use WhatsApp, so can't say about it, but iMessage is definitely sluggish and unusable.

Turning off Real-time file system protection instantly making iMessage reacting normal.

As "sudsandsoda" previously mentioned, turning off Settings > File-system Protection > Scan on \ File open makes iMessage reacting normal as well.

Any upcoming fix for this is appreciated.

Thanks

 

 

[bachv 0]

Same here, affects Messages and WhatsApp, is gone as soon as I disable RTFSP. macOS 15.1 with ESET Endpoint Security v8.1.6.0.

[CF feedback 0]

Experiencing the same issue, and I confirmed with Apple to trouble shoot and get to the root cause. Typing it not delayed in any other program - just iMessage. And oddly, it only happens with the keyboard but not using dictation. 

[TItop 0]

Same issues  here. Anyone has a fix for that?

[Marcos 5,468]

Please raise a support ticket for help with further investigation of the issue.

[Marcos 5,468]

Has anybody tried upgrading to macOS 15.2 beta 2 or 3 to see if it makes a difference?

[w3ss 1]

6 hours ago, Marcos said:

Please raise a support ticket for help with further investigation of the issue.

Raised a ticket for the problem

 

304914

[thegreg 0]

I'm also having the same issue. Disabling the realtime protection immediately made the lag stop.  I'm on MacOS 15.1, not willing to install a beta OS, sorry.

[TItop 0]

Kind of strange that since this problem was identified ( weeks now), no reaction or comment, from ESET or any ESET staff. not professional

[Marcos 5,468]

While we were able to reproduce it with macOS 15.1, we couldn't with 15.2 beta 2. So far the issue appears to be OS-related, hence the question if anybody has installed 15.2 beta and still experiences the issue.

[lllusion 2]

Yes, this is a known issue. I can confirm that disabling R-tFSP resolves the typing delay issue in Messages. Since I want that protection I'll live with the delay for now and hope that 15.2 does in fact resolve the issue and that it gets released soon.

Note: Curiously, this issue affects Messages and WhatsApp but not Signal. 🤨

[Marcos 5,468]

Also discussed at https://discussions.apple.com/thread/255822080?sortBy=rank&page=1 where more users mentioned they had no AV installed.

[John H 0]

This can be worked around by disabling "scan on -> file open". But clearly that is not something most AV users would want to disable.

I can see that WhatsApp is writing to ~/Library/Group Containers/group.net.whatsapp.WhatsApp.shared/Logs/WhatsApp_2/whatsapp-2024-11-25-11-04-18-1351-WhatsApp-1481.log  (numbers changing obviously) every  3ms while you type.

There's evidence that each write to the logfile involves re-opening the file. I ran `lsof` while typing, and the file appears in some samples and not others.

So perhaps while we type ESET is scanning this ~1Mb logfile hundreds of times per second.

However I added the directory containing this file to "Performance exclusions" and that did not help.

[John H 0]

To add, the 100s of log lines per second are of this form:

 

11:04:19.644 [  11513] [main-thread   ] [F] LL_A ai/manager/feature/bonsai-entry-point-not-enabled
11:04:19.644 [  11513] [main-thread   ] [F] LL_A ai/manager/composer-new-chat-ai-status/disabled
11:04:19.647 [  11513] [main-thread   ] [F] LL_A ai/manager/feature/bonsai-entry-point-not-enabled
11:04:19.647 [  11513] [main-thread   ] [F] LL_A ai/manager/composer-new-chat-ai-status/disabled
11:04:19.650 [  11513] [main-thread   ] [F] LL_A ai/manager/feature/bonsai-entry-point-not-enabled
11:04:19.650 [  11513] [main-thread   ] [F] LL_A ai/manager/composer-new-chat-ai-status/disabled
11:04:19.652 [  11513] [main-thread   ] [F] LL_A ai/manager/feature/bonsai-entry-point-not-enabled

Evidently the text input is going into an expensive loop, asking for some AI feature and retrying each time it's declined.

[Peter Randziak 1,186]

Hello guys,

one of the users, experiencing the issue confirmed that it was resolved in the macOS Sequoia 15.2 Beta 3 (from Developer channel)

Peter

[Robertos 68]

Hello John,

The log you mentioned doesn't appear to be from the ESET product. It seems more likely to be from an Apple service, which further supports the conclusion that this issue may be related to macOS itself.

Please let me know if you need any further assistance.