timeout: Timed out receiving message from renderer: 300.000

[BoyuanFeng]

Summary

I am profiling the wasm performance of a function, which runs for more than 5 minutes. Then I get the following error:

got: {"sessionId":"6eed583a92cc19dbbecdfb0c114d7d25","status":21,"value":{"message":"timeout: Timed out receiving message from renderer: 300.000\n (Session info: headless chrome=101.0.4951.64)\n (Driver info: chromedriver=101.0.4951.64 (d1daa9897e1bc1d507d6be8f2346e377e5505905-refs/branch-heads/4951@{#1208}),platform=Linux 5.15.0-27-generic x86_64)"}}

The reason is that there is a 300-second timeout setting in WebDriver [1]. Is it possible to add an interface to set that in wasm-bindgen?

[1] https://developer.mozilla.org/en-US/docs/Web/WebDriver/Timeouts

Additional details

1. I use this command to run wasm-pack test --headless --chrome --release
2. I checked previous time-out issues [2, 3]. But these are different from the timeout I am facing.

[2] #2261
[3] #2036

[ranile]

You should be able set the timeout via webdriver.json file. See documentation.

[BoyuanFeng]

Thanks for quick reply! I tried webdriver.json with
{ "goog:chromeOptions": { "args": [ "disable-timeouts-for-profiling" ] } }

However, this one does not work... The same timeout error appears. Do you have any example of how to set the page load timeout in webdriver.json?