Use of Groups for Tabs Causes Freezup

@Max2 ,

Requires study.

Using as tools that help you to see all of the processes involved – whichever of the following are available on your computing device:

  • OS Actvity Monitor
  • OS Task Manager
  • Brave Browser Task Manager
  • OS Performance Monitor
  • OS Resource Monitor

. . . and using for guidance:

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”.