Under Ubuntu 26.04 High memory usage optimization full record | Same as 60 tags, Win10≈7GB, Ubuntu skyrocketed to 20GB row pit record

Environment: Ubuntu 26.04 + Google Chrome For the official version, 60 tabs (about 50 different domain names), compared with the memory difference of the same configuration in Windows 10, gradually optimized from 2GB of no-load and 19GB of full load to a reasonable range.

1. Phenomenon: There is a huge gap between system memory

1. The original question

• windows10:4 windows 60 tags (50 exotic names), Chrome memory is stable 6~8GB;
• Ubuntu default chrome: the same number of tags, no-load single label occupies ≈ 2.0~2.4GB, open the full 60 tags and soar directly to18~20GB, far more than double Windows.

Figure 1: Screenshot of the memory usage of the whole machine in the first 60 tags of the optimization (the original full load is 19GB+)

• Comparison reference: The no-load usage of Chrome in the same environment also reaches 3GB.
  Figure 2: The no-load usage of Chrome in the same environment also reaches 3GB

2. Root cause conclusions

chrome The Linux version forces the ‘Site Isolation’ security mechanism to be enabled by default:Different domain name pages force the creation of independent sandbox rendering process, 50 domain names = at least 50 isolated processes; the Windows side Chrome intelligent homologous merge process, the natural memory usage is lower.

After I installed Ubuntu, I logged in in the Chrome browser, and then automatically synchronized the data of the cloud to the local.

Note: Site isolation can be closed through startup parameters, but it will slightly reduce the security level of browser vulnerability isolation, and wallet users can choose as needed,This article does not have a practical plan 2, only for knowledge retention.

2. Step-by-step optimization practice (retain Google account login, bookmark, password throughout the whole process, do not reset the browser configuration)

(1) Simplify the synchronization item: cut off the background synchronization invisible process from the source

Path: Settings → You are synced with Google → Customize
✅ Only open 3 items:Bookmarks, addresses and other information, passwords and pass keys
❌ Close all: remaining sync items such as history, extensions, settings, open tabs, reading lists, etc.
Figure 6: Screenshot of the configuration of Google account custom synchronization check

Effect: No longer synchronize old device extensions and browser configuration in the cloud, and prevent the resident memory of stolen memory in the background synchronization service.

(2) System item optimization: turn off the background resident, hardware AI preloading

Path: Settings → System

1. Close:Continue to run background apps after closing Google Chrome
2. Close:Use Graphics Acceleration
3. Close:Device-side AI

Figure 5: Screenshot of three system settings off configuration

Function: Eliminate background residual process, abnormal graphics card leakage, and local AI model resident memory.

(3) Privacy security optimization: shut down advertising tracking, website background residency

1. Advertising privacy settings: advertising themes, website recommendation advertisements, advertising performance measurementAll three items are closed, stop browsing the personalized process of data collection;
   Figure 7: Screenshots of all ad privacy settings are turned off

1. Website settings → background synchronization: The global background is prohibited from sending and receiving data silently in the background of the website, and the child process is destroyed when the page is closed.
   Figure 8: Screenshot of the website background synchronization permission close setting

(4) Performance configuration: full memory recovery mechanism

Path: Settings → Performance

1. Memory saver: set tomaximum, there is no whitelist resident site;
   Figure 9: Performance page memory savings set to maximum screenshot

(5) Extension and streamlining: wallet expansion is temporarily enabled on demand

Native Phantom, MetaMask and other wallet extensions are all disabled, and only the Stylus style plugin is enabled.
Figure 4: Screenshot of the enabled status of the extended management page

The common problem of Linux wallet expansion: idle and continue to poll the data on the RPC chain, it is very easy to memory leakage, and the non-use period is always disabled.

(6) Cache cleaning: regularly clear the redundant disk cache (this key memory reduction operation)

Shortcut keys Ctrl+Shift+Delete, time range: unlimited time
Check: browse records, cache pictures and files; uncheck cookies, passwords, and form data.
Figure 11: Clear browsing data and check the configuration screenshot

Full load memory before cleaning: 18.55GB; after clearing the cache + restarting chrome: the full load is directly reduced to9.99GB, a single optimization releases nearly 9GB of redundant memory.
Figure 12: Screenshot of the memory of the whole machine after clearing the cache and restarting (about 10GB after optimization)

Optimization logic: Long-term browsing and stacking resource caches will continue to mount memory, and regular cleaning is the key to long-term memory control.

3. Two sets of subsequent long-term optimization plans (choose one of two, plan 2 has not been implemented in this article)

Option 1｜Retain native site isolation (priority recommendation, wallet security is optimal, this article is being used)

Suitable for long-term use of Web3 wallets, unwilling to sacrifice sandbox security:

1. Labels are opened in batches: only 15~20 tags are opened in a single time, and the idle is automatically recycled by ‘maximum memory saving’;
2. Low-frequency tag archive: install OneTab to collect idle labels, and destroy redundant rendering processes;
3. Maintenance cycle: Repeat only the cache + history cleaning operation every 30 days.

Scenario 2｜Close site isolation (extreme control memory, benchmark firefox usage,This article is not practical, only theoretical reference)

If you need to further depress the memory, unforce the domain name isolation via the startup parameters:

--disable-site-isolation-trials --disable-background-networking --disable-preconnect

After configuration, the memory of the theoretical 60 tag can be pressed to 7~8GB; the isolation and isolation are slightly reduced, and the safety protection is slightly reduced, and the self-test on demand.

4. Comparison of data before and after optimization

Figure 3: Chrome Task Manager Process Occupancy Details

5. Summary

1. linux version chrome high memoryThe core is site isolation mechanism + web cache stacking + wallet expansion background pollingThree factors are superimposed;
2. I don’t want to change the underlying startup parameters, and I can cut off nearly half of the memory by ‘simplifying synchronization + full performance + clearing cache + batching labels’;
3. Pursue the ultimate memory and insensitive security loss, add site isolation and shutdown parameters, and directly align Windows/Firefox memory performance.

Applicable people: Linux desktop heavy chrome multi-tab users, web3 wallet high-frequency users