CoreLibs icon indicating copy to clipboard operation
CoreLibs copied to clipboard

Tracking issue for apps that start using 100% CPU due to how sockets are closed by a network extension

Open Chinaski1 opened this issue 3 years ago • 10 comments

The list of problematic apps:

  1. Adobe Creative Cloud
  2. Mail.app
  3. netbiosd

The issue explanation is here: https://developer.apple.com/forums/thread/681135

Since the original report we implemented a workaround that mitigates the issue, but there's still a small possibility of that happening.

Original report:

  • OS version: 11.3 Beta (20E5224a)
  • AdGuard Version: 2.5.3.955 release (CL-1.7.200)
  • Filtering method: Network extension
  • Adobe Creative Cloud version: Version 2.4.0.41 (2.4.0.41)

Original appeal

Chinaski1 avatar Apr 09 '21 14:04 Chinaski1

Any progress?

akiltopu avatar May 25 '21 09:05 akiltopu

It is not 100% reproducable but we've been able to reproduce it and are now trying to find the reason of this behaviour (yet another Apple bug or API misusage).

sfionov avatar May 27 '21 11:05 sfionov

Thanks @sfionov is there any ETA? I am unable to use Adguard as of now until the issue will be fixed - unless there's any workaround? Also, do you know if this is happening only with the Mac App, or does it still happen even if I just have the Chrome plugin?

marcellosilvestri avatar May 28 '21 14:05 marcellosilvestri

Hi all!

@wiredmark @akiltopu

I would like to clarify some information. Please specify if you are using system proxy settings? (System preferences -> Network -> Advanced -> Settings)

Chinaski1 avatar May 28 '21 15:05 Chinaski1

Hi @Chinaski1, nope, nothing is flagged in that screen

marcellosilvestri avatar May 30 '21 18:05 marcellosilvestri

This happens because of Apple's misbehaviour, and a way network apps processes socket errors. macOS doesn't indicate read error on sockets that existed before starting AdGuard protection - only when they try to write something. That confuses apps a lot.

This is also reproducible with Apple SSH connected to non-standard port (because standard port is excluded in AdGuard).

Reported to Apple: FB9125326

sfionov avatar Jun 02 '21 13:06 sfionov

There's no workaround right now but killing CPU-consuming process will help.

sfionov avatar Jun 02 '21 13:06 sfionov

Also reported to Apple developer forums: https://developer.apple.com/forums/thread/681135

sfionov avatar Jun 02 '21 13:06 sfionov

I've been having this issue for years and had no idea adguard was the cause.

Horizon531 avatar Aug 23 '22 10:08 Horizon531

To be precise the bug is Apple's :(

Since v2.8 we implemented a workaround that should've mitigated it, but there's still a small possibility of that happening.

ameshkov avatar Aug 24 '22 19:08 ameshkov