The 1,000.00 plus MB of Memory being used, is a summation of processes that make up a Brave aggreggate . . . and not unusual. A similar amount is found on the Mac OS, when all such values are added; for example:
–
–
Updating this reply . . .
Re “Task Manager - Brave” (the 2nd of your two screenshots, above): There are 18 proccesses that make up the Brave aggregate at that moment:
- Browser
- GPU Process
- Spare Renderer
- Extension: Brave
- Extension: Enhancer for YouTube™
- Extension: I don’t care about cookies
- Extension: Pop up blocker for Chrome™ - Poper Blocker
- Extension: uBlock Origin
- 5 Tabs
- Utility: Audio Service
- Utility: Bad Ads Service
- Utility: Bad Ledger Service
- Utility: Network Service
- Utility: Storage Service
–
Re Chromium link mentioned earlier
"https://www.chromium.org/developers/memory-usage-backgrounder/”
Multi-Process Model Background
To understand Chromium’s memory usage, let’s understand the multi-process model. Unlike other browsers, Chromium is divided into multiple processes. When Chromium starts up, it will initially have two processes. One process is the browser process which controls the main browser functionality, and the other is the initial renderer process , which runs the Blink rendering engine and JavaScript (V8). Each time you open a new tab in Chromium, you’ll likely get a new renderer process. With typical browsing, it is common to see 5-7 chrome.exe processes active. Further, if you utilize plugins, apps, or extensions, they may also execute within independent processes. All of Chromium’s processes, whether it is a browser process, a renderer process, or a plugin process, will show under the Task Manager as “chrome.exe”.