websockets

[klh]

Just a heads up, did something similar awhile back and ran into some serious issues with the cdp and ws in network layer.
stuff crashes hard if you push over 80-120mb of messages through the ws interface (when inspecting, the browser is fine with it).

so a good idea is to implement a chunked reader that keeps the memory footprint low when ingesting, and only offer a "download message" for very large blobs of data.

[fcavallarin]

Thanks a lot for the heads-up - this is really useful context.

Right now, Wirebrowser reads CDP messages as a single payload, so very large frames end up hitting the WS limits.
CDP itself delivers heap snapshots in chunks for this exact reason, so a similar approach here makes a lot of sense.

A chunked reader + “download full message” fallback definitely seems like the right direction. I’ll explore a streaming approach so huge blobs don’t need to be transferred all at once.

Really appreciate you flagging this early.