AdguardTeam / AdguardTeam/AdGuardMiniForMac

Memory footprint reduction

Open
#1,201 3 comments 1 reaction 1 assignee Assigned to @forcomprehension View on GitHub
Feature request Priority: P4 Resolution: Done Status: Ready for Deployment Version: AdGuard v3.0
Dominant language
Swift
Stars
1.2k
Forks
83
PR merge metrics
PR metrics pending

Description

### Issue Details

On macOS (MacBook with 8GB RAM), AdGuard’s total memory usage (Safari extension + menu bar/background app) is disproportionately high compared to similar ad-blocking solutions.

Memory consumption is split across:

- Safari extension component
- Menu bar/background application

Combined usage is typically around ~350MB in normal browsing conditions with standard filter lists enabled. This is significantly higher than comparable lightweight extensions. For example, uBlock Origin Lite operates at under ~20MB with equivalent filtering configurations, while still providing effective ad blocking.

The issue is that AdGuard’s total memory footprint (Safari extension + menu bar/background application) remains relatively high as a baseline, even when browsing activity is light. Memory usage does not appear to scale proportionally with active tab load or filtering demand, which results in unnecessary pressure on system memory. On 8GB machines this contributes to increased swap usage and reduced overall system responsiveness.

Image

Image

Image

### Proposed solution

Reduce memory footprint inline with comparable Safari browser extension ad blockers.

### Alternative solution

_No response_

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.