[🐛 Bug]: out of memory, 32bit chrome

[GlobalMe2017]

Description

i use OKX wallet extension to connect to some WEB3 website.

OKX wallet extension has got more than 1G ram, and when selenium open a new tab, it shows out of memory in the new tab.

and selenium and chrome logs shows it could not connect to the chrome, then selenium stopped but not ended.
if i manually click on the reload button on the "out of memory" page, then there will be a GC log, then selenium resume the connection and the selenium code start running again.

please help me:

1. i know there is a limit of memory of 1G for 32bit chrome for each tab and it seems no solution to enlarge it with 32bit chrome. but how could i monitor the tabs memory? then if i find out OKX wallet has more than 1G, how to do with it? close the tab or ?

2. when "out of memory" happens, what to do to avoid selenium stops? how to automatically make it run again?

Thanks very much.

Reproducible Code

it is the log when "out of memory", the selenium lost the connection to the chrome.

Traceback (most recent call last):
  File "urllib3\connectionpool.py", line 787, in urlopen
  File "urllib3\connectionpool.py", line 536, in _make_request
  File "urllib3\connectionpool.py", line 367, in _raise_timeout
urllib3.exceptions.ReadTimeoutError: HTTPConnectionPool(host='localhost', port=56182): Read timed out. (read timeout=120)

Debugging Logs

it is the GC if manually click on reload on "out of memory" page:

<--- Last few GCs --->

[16112:32C04000]   538110 ms: Scavenge (during sweeping) 983.3 (1024.5) -> 982.6 (1024.5) MB, pooled: 0.0 MB, 11.45 / 0.00 ms (average mu = 0.387, current mu = 0.404) allocation failure;
[16112:32C04000]   539286 ms: Mark-Compact 986.1 (1026.5) -> 972.1 (1019.8) MB, pooled: 0.0 MB, 1060.25 / 0.01 ms (average mu = 0.319, current mu = 0.239) allocation failure; scavenge might not succeed


<--- Last few GCs --->

[17784:47404000]   636194 ms: Mark-Compact 991.8 (1036.9) -> 985.8 (1032.5) MB, pooled: 8.8 MB, 858.25 / 0.01 ms (average mu = 0.492, current mu = 0.290) allocation failure; scavenge might not succeed
[17784:47404000]   637586 ms: Mark-Compact (reduce) 999.2 (1040.0) -> 995.7 (1031.8) MB, pooled: 0.0 MB, 87.76 / 0.06 ms (+ 659.0 ms in 128 steps since start of marking, biggest step 23.5 ms, walltime since start of marking 1185 ms) (average mu = 0.491, c

---

ℹ️ Last known working version: 4.36

[selenium-ci]

@GlobalMe2017, thank you for creating this issue. We will troubleshoot it as soon as we can.

Selenium Triage Team: remember to follow the Triage Guide

[selenium-ci]

Hi, @GlobalMe2017.
This issue has been determined to require fixes in ChromeDriver.

You can see if the feature is passing in the Web Platform Tests.

If it is something new, please create an issue with the ChromeDriver team.
Feel free to comment the issues that you raise back in this issue. Thank you.