Error disposing browser context

[imiric]

This is the issue that triggered #510, which still happens on current main (db80f94). The event loop corruption was fixed in k6 (grafana/k6#2693), but we still need to fix this trigger issue here.

It can be relatively easily reproduced on Cloud with the same script from #510. Running a test with this script with 1VU for 1h often produces this log:

Uncaught (in promise) disposing browser context: disposing browser context ID EFE761C1AE3FFA4EC51442683B3589D2: sending a message to browser: websocket: close 1006 (abnormal closure): unexpected EOF executor=constant-vus scenario=default		test_run_id: 141246
communicating with browser: websocket: close 1006 (abnormal closure): unexpected EOF category=cdp elapsed=23416 ms goroutine=1075082		test_run_id: 141246
process with PID 168213 unexpectedly ended: signal: killed category=browser elapsed=8 ms goroutine=1075068		test_run_id: 141246

The behavior is that the browser process is killed, likely because the context is cancelled, but it's not clear why that would happen during the BrowserContext.Close() call, which happens from Page.Close(), which is called before Browser.Close().

[imiric]

I'm increasing the priority of this, since it's the most common issue in Cloud test runs now.

[imiric]

After #555, we no longer see this issue in the Cloud 🎉

So I'm closing this.