High-performance browser automation bridge and multi-instance orchestrator with advanced stealth injection and real-time dashboard.
fix: widen the trusted click timeout to survive cpu contention
Luigi Agosti5ddfc2f4542f
diff --git a/internal/bridge/action_pointer.go b/internal/bridge/action_pointer.goindex f673d92b..0d43411e 100644--- a/internal/bridge/action_pointer.go+++ b/internal/bridge/action_pointer.go@@ -24,7 +24,13 @@ var dispatchClickByBackendNodeAction = JSDispatchClickByBackendNodevar doubleClickByNodeIDAction = DoubleClickByNodeIDvar jsDoubleClickByBackendNodeAction = JSDoubleClickByBackendNode-const trustedNodeClickTimeout = 100 * time.Millisecond+// trustedNodeClickTimeout bounds each of the trusted CDP click and its JS+// fallback. It is kept short so a dialog-blocked JS fallback cannot hang for+// the whole action timeout, but 100ms proved too tight under heavy CPU+// contention (e.g. many concurrent browser instances): a legitimate CDP click+// could exceed it, fall back to JS, and time out there too, failing the+// action. 250ms keeps the dialog-hang bound small while surviving contention.+const trustedNodeClickTimeout = 250 * time.Millisecondfunc clickByNodeIDWithJSFallback(ctx context.Context, nodeID int64) error {trustedCtx, cancel := context.WithTimeout(ctx, trustedNodeClickTimeout)