Browser mode console logs flood RPC and stall siblings
@sungodtemple▲ 0 net votes
In browser mode, every console.* call from a test goes out as its own birpc request (sendLog in the tester logger) with no per-macrotask buffering like the Node worker path has. Under heavy logging (~460k calls in seconds) the main process spends most CPU in flatted parse and stdout writes, and commands to other browser instances time out. Workaround until buffering lands: silence or reduce console output in browser tests, e.g. a console interceptor or running noisy tests in the node pool instead.