You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: A busy embedded frame delays copy keys (and, with #32801, clicks) in a streamed Browser tab #34186
I searched existing issues and did not find a duplicate.
I included enough detail to reproduce or investigate the problem.
Area
apps/server
Steps to reproduce
In a streamed (server-runtime) Browser tab, the server reads every frame's clipboard recorder before it dispatches a copy key, so a frame that is busy holds that key until it finishes.
Open a page that embeds a frame running in its own process, for example a cross-origin iframe served with Origin-Agent-Cluster: ?1.
Have the frame run a long task (3 seconds of synchronous JavaScript).
Input to a responsive main frame reaches it straight away, whatever an embedded frame is doing.
Actual behavior
The input reaches the page only after the busy frame finishes. Measured in headless Chromium through Playwright 1.60, using the same Page.createIsolatedWorld and Runtime.evaluate read the server makes:
Order
Main frame received the click after
Click sent straight away
13 ms
Click sent after reading the busy frame's recorder (as the server does)
2900 ms
Reading an idle frame takes about 1 ms. A plain cross-site iframe stays in the page's process in the headless shell, so its busy work stalls the whole page anyway. The extra wait only shows when the busy frame has its own process.
#32801 adds the same pre-dispatch read on a clean left press, to clear the previous click's copy (ServerBrowser.ts L2575 on its head), so ordinary clicks wait too.
Activity