Memory Runaway Bug affecting Brave (Chromium 147.0.7727.137) on Windows 11

Browser Support
, ,
1

Description of the issue: High Memory utilisation with runaway Brave processes on the latest version of the Browser on Windows 11

Steps to Reproduce (add as many as necessary): Occurs after 20 mins of usage in any aspect.

Actual Result (gifs and screenshots are welcome!): Having to force close the browser to regain Memory

Expected result: Browser should allocate memory correctly, but the latest Chromium appears to be buggy.

Reproduces how often: Every time I use the browser.

Operating System and Brave Version(See the About Brave page in the main menu): Windows 11 (Chromium 147.0.7727.137)

Additional Information:

2

@xdunal3306

Brave Support may ask for a screenshot showing both the Brave Browser Task Manager and the Windows OS Task Manager - example:

BBTaskMgrWinTaskMgr
BBTaskMgrWinTaskMgr1936×964 114 KB

Note the columns in the following Brave Browser Task Manager window screenshot.

Memory footprint | CPU | Process ID | Image cache | Script cache | GPU memory | JavaScript memory

BBTaskMgrColumnswDetails
BBTaskMgrColumnswDetails1536×716 47.2 KB

→ Thus, Workload Details Revealed ←

Suggest:

Create a new user Profile for Testing:

Create and use AN ADDITIONAL Brave Browser user Profile (Menu --> More tools --> Add profile) - only ← meaning: Do not have any other Brave Browser user Profile tabs/windows open.

When creating this new Brave Browser user Profile for test purposes

  • Do not import anything.
  • Do not add any extensions.
  • Do not allow/enable any Brave Browser “bells and whistles” such as Brave Rewards, Brave Talk, etc.

IF this test Brave Browser user Profile does not present your problem, then possibly, the profile that you have been using, has a problem . . . and that might be caused by one or more extensions, or too many tabs ← complex/conundrum.

Extensions Tests:
  • test by disabling all extensions
  • test by enabling each extension individually
  • test by uninstalling all extensions
  • test by installing each extension individually
  • test combinations of extensions
  • test order of installation of extensions
3

Thank you.. as soon as it happens again (more than likely, later today) I will capture and attach the recommended screenshots.

Al