All committers have signed the CLA.

You set it in the driver after creating it: driver.set_page_load_timeout(30), for example.

You set it in the driver after creating it: driver.set_page_load_timeout(30), for example.

# Part of the code of my program

options = webdriver.ChromeOptions()
options.add_experimental_option("debuggerAddress", f"127.0.0.1:{self.port}")
options.timeouts = {"pageLoad": 60000}
try:
   self.chromeDriver = webdriver.Chrome(service=Service(ChromedriverPath), options=options)
except Exception as err:
    print(err) # Message: timeout: Timed out receiving message from renderer: 300.000

I'm trying to solve this problem
I must set the timeout only before receiving this error, or I will have to wait 300 seconds to continue execution

That is different, you seem to be having issues creating the session. First try without this
options.add_experimental_option("debuggerAddress", f"127.0.0.1:{self.port}"), and then debug from that point.

If you have more questions, please use the following channels https://www.selenium.dev/support/

Running for a long time will cause chrome to get stuck

那是不一样的，你好像在创建会话时遇到问题。首先尝试不使用this options.add_experimental_option("debuggerAddress", f"127.0.0.1:{self.port}")，然后从那一点开始调试。

如果您有更多问题，请使用以下渠道https://www.selenium.dev/support/

The session has been running for a long time Running for a long time will cause chrome to get stuck
All GUI functions of Chrome are invalid The manual shutdown procedure also fails
I have to force the end of chrome and restart the remote binding
Each re-link must wait 300 seconds

@diemol we should encourage setting timeout values in options instead of after session starts.

@symonk can you check this logic? I can't tell what we support now vs what this code allows.

I see. I was checking the docs and saw something else. Good to know.

Codecov Report

Patch coverage has no change and project coverage change: -0.02 ⚠️

Comparison is base (6a47cc3) 55.14% compared to head (f66639e) 55.13%.

❗ Current head f66639e differs from pull request most recent head 48d883b. Consider uploading reports for the commit 48d883b to get more accurate results

📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more

@@            Coverage Diff             @@
##            trunk   #11623      +/-   ##
==========================================
- Coverage   55.14%   55.13%   -0.02%     
==========================================
  Files          85       85              
  Lines        5652     5652              
  Branches      228      227       -1     
==========================================
- Hits         3117     3116       -1     
- Misses       2307     2309       +2     
+ Partials      228      227       -1     

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

It's one of the things added with w3c that probably needs to be updated in our docs in multiple places.

The matter involved in the end should be very complex
Should lose a few hairs
thank you for all you do Thank you for open source software

Thanks, I think this is a slightly better implementation than what existed before (Enforcing every timeout was provided else giving an ambiguous error) to now making sure all keys are in the allowed sequence, this is ok for now. In future I think we should probably extract the 'known' keys and throwaway the rest without causing an error).