From 49aa0ad1a9c1936bcf981fbe1233d18a0ea51912 Mon Sep 17 00:00:00 2001
From: Karl Seguin <k@openmymind.io>
Date: Mon, 18 May 2026 19:44:25 +0800
Subject: [PATCH] On blocking read failure, break from loop

Blocking read failure almost certainly means a disconnect client. As-is, that's
an endless loop. Instead, fail the request.
---
 src/browser/HttpClient.zig | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/src/browser/HttpClient.zig b/src/browser/HttpClient.zig
index 127a4a32..6f2d19b7 100644
--- a/src/browser/HttpClient.zig
+++ b/src/browser/HttpClient.zig
@@ -530,7 +530,9 @@ pub fn syncRequest(self: *Client, allocator: Allocator, req: Request) !SyncRespo
         switch (status) {
             .cdp_socket => {
                 const cdp = self.cdp_client.?;
-                _ = cdp.blocking_read(cdp.ctx);
+                if (cdp.blocking_read(cdp.ctx) == false) {
+                    return error.ClientDisconnected;
+                }
             },
             .normal => continue,
         }