Repository navigation
[Feature]: cdpSession does not have a timeout waiting mechanism. #1810
Description
🚀 Feature Request
It don't rely on Supplier as a termination condition . Instead, it relies on WaitableResult - internally registering events through sendMessageAsync() via a callback mechanism.But if the browser never returns a message ⇒ waitable.isDone() is always false ⇒ while never exits ⇒ the thread hangs. So can PlayWright add a wait timeout mechanism?
Example
No response
Motivation
When multiple threads are tested, some threads may hang and not execute tasks.
Activity
yury-s commentedon Oct 19, 2026
Hi, the Playwright bot looked into this on my behalf.
This is being added:
CDPSession.sendgets atimeoutoption in Playwright 1.65 (microsoft/playwright#43404). It defaults to0, meaning no timeout, and throwsTimeoutErrorwhen the browser doesn't answer in time. Java picks it up with the 1.65 driver roll. Until thenCDPSession.sendwaits for the response indefinitely, as you describe.Separately, #2006 (merged after 1.63) makes calls that take a timeout throw
TimeoutErroron the client even when the driver process itself stops responding.Investigated locally by the Playwright bot