The Network-extension Process Is Consuming More Than 100% Of The CPU On 2.17.0.1955 Nightly

by ADMIN 92 views

The network-extension process is consuming more than 100% of the CPU on 2.17.0.1955 nightly

The AdGuard network-extension process is a crucial component of the AdGuard for Mac Nightly application, responsible for filtering and blocking online content. However, in the 2.17.0.1955 nightly version, users have reported that the network-extension process is consuming more than 100% of the CPU, leading to performance issues and system slowdowns. In this article, we will delve into the details of this issue, explore possible causes, and provide potential solutions to resolve the problem.

Before we dive into the issue, let's take a look at the system configuration that was used to reproduce the problem:

  • AdGuard version: 2.17.0.1955 nightly
  • Browser version: Arc 1.92
  • OS version: macOS Sequoia 15.5 dev beta
  • Ad Blocking: AdGuard Base filter
  • Privacy: AdGuard Tracking Protection filter, AdGuard URL Tracking filter
  • Social: No response
  • Annoyances: AdGuard Annoyances filter
  • Security: Phishing URL Blocklist, Online Malicious URL Blocklist, Scam Blocklist by DurableNapkin, uBlock Origin – Badware risks, NoCoin Filter List
  • Other: AdGuard DNS filter
  • Language-specific: AdGuard Japanese filter
  • DNS server: AdGuard DNS
  • DNS protocol: DNS-over-QUIC
  • Custom DNS: No response
  • Stealth Mode options: Block trackers, Remove tracking parameters, Hide your search queries, Send Do-Not-Track signals

The issue was reproduced by following these steps:

  1. Run AdGuard for Mac Nightly
  2. Use it for a while
  3. com.adguard.mac.adguard.network-extension process CPU usage exceeds 100% (reaches 200-300%)

The expected behavior is that the com.adguard.mac.adguard.network-extension process CPU usage stays between 10-20%.

The actual behavior is that the com.adguard.mac.adguard.network-extension process CPU usage exceeds 100% (reaches 200-300%).

Based on the system configuration and the steps to reproduce the issue, there are several possible causes that could be contributing to the problem:

  • Inefficient filtering: The AdGuard network-extension process may be using an inefficient filtering algorithm, leading to high CPU usage.
  • DNS-over-QUIC issues: The use of DNS-over-QUIC may be causing issues with the network-extension process, leading to high CPU usage.
  • Stealth Mode options: The Stealth Mode options may be causing issues with the network-extension process, leading to high CPU usage.
  • Filter updates: The filters may be updated too frequently, leading to high CPU usage.

Based on the possible causes, here are some potential solutions to resolve the issue:

  • Update to the latest version: Update to the latest version of AdGuard for Mac Nightly to see if the issue is resolved.
  • Disable Stealth Mode options: Disable the Stealth Mode options to see if the issue is resolved.
  • Switch to a different DNS protocol: Switch to a different DNS protocol, such as DNS-over-TLS, to see if the issue is resolved.
  • Update filters: Update the filters to the latest version to see if the issue is resolved.
  • Reset AdGuard settings: Reset AdGuard settings to their default values to see if the issue is resolved.

The network-extension process consuming more than 100% of the CPU on 2.17.0.1955 nightly is a serious issue that can cause performance problems and system slowdowns. By understanding the possible causes and potential solutions, users can take steps to resolve the issue and improve their AdGuard for Mac Nightly experience.

The user has reported that the issue has stabilized on the Beta version, suggesting that the issue may be specific to the nightly version.

Based on the information provided, we recommend that users:

  • Update to the latest version: Update to the latest version of AdGuard for Mac Nightly to see if the issue is resolved.
  • Disable Stealth Mode options: Disable the Stealth Mode options to see if the issue is resolved.
  • Switch to a different DNS protocol: Switch to a different DNS protocol, such as DNS-over-TLS, to see if the issue is resolved.
  • Update filters: Update the filters to the latest version to see if the issue is resolved.
  • Reset AdGuard settings: Reset AdGuard settings to their default values to see if the issue is resolved.

By following these recommendations, users can potentially resolve the issue and improve their AdGuard for Mac Nightly experience.
Frequently Asked Questions (FAQs) about the network-extension process consuming more than 100% of the CPU on 2.17.0.1955 nightly

A: The network-extension process is a crucial component of the AdGuard for Mac Nightly application, responsible for filtering and blocking online content.

A: There are several possible causes, including inefficient filtering, DNS-over-QUIC issues, Stealth Mode options, and filter updates.

A: To update to the latest version of AdGuard for Mac Nightly, follow these steps:

  1. Open AdGuard for Mac Nightly.
  2. Click on the "Help" menu.
  3. Select "Check for updates".
  4. If an update is available, click on the "Update" button to download and install the latest version.

A: To disable Stealth Mode options, follow these steps:

  1. Open AdGuard for Mac Nightly.
  2. Click on the "Preferences" menu.
  3. Select "Stealth Mode".
  4. Uncheck the boxes next to each Stealth Mode option to disable them.

A: To switch to a different DNS protocol, follow these steps:

  1. Open AdGuard for Mac Nightly.
  2. Click on the "Preferences" menu.
  3. Select "DNS".
  4. Select a different DNS protocol from the dropdown menu.

A: To update filters, follow these steps:

  1. Open AdGuard for Mac Nightly.
  2. Click on the "Preferences" menu.
  3. Select "Filters".
  4. Click on the "Update" button to download and install the latest filters.

A: To reset AdGuard settings to their default values, follow these steps:

  1. Open AdGuard for Mac Nightly.
  2. Click on the "Preferences" menu.
  3. Select "Reset settings".
  4. Confirm that you want to reset the settings to their default values.

A: The issue may be specific to the nightly version due to the experimental nature of the nightly builds.

A: Yes, you can contact AdGuard support for further assistance. Please provide as much detail as possible about the issue you are experiencing, including the steps you have taken to troubleshoot the problem.

A: Yes, there are several known workarounds for this issue, including disabling Stealth Mode options, switching to a different DNS protocol, and updating filters. However, these workarounds may not resolve the issue completely.

A: AdGuard is working to resolve the issue and may release a patch in the future. However, no timeline has been provided for the release of the patch.