Skip to content

brw v0.5.1 — resilient no-tab_id resolution

Choose a tag to compare

View all tags
@revitteth revitteth released this 01 Jul 09:22
v0.5.1
This tag was signed with the committer’s verified signature.
revitteth Max Revitt
SSH Key Fingerprint: hSu0lwdvgGmc075P3libkV/1P37R7Y51dFjU4RAiWr4
Verified
Learn about vigilant mode.
1407183
This commit was signed with the committer’s verified signature.
revitteth Max Revitt
SSH Key Fingerprint: hSu0lwdvgGmc075P3libkV/1P37R7Y51dFjU4RAiWr4
Verified
Learn about vigilant mode.

brw v0.5.1 — resilient no-tab_id resolution (fixes a 20s latency cascade)

Fixes a regression from v0.5.0's default tab isolation: when a browser's extension stops answering open_tab — e.g. a real Chrome whose extension hasn't been reloaded to match the new daemon, or a transiently wedged extension — the isolation auto-open re-fired on every no-tab_id action and each hit the full 20s bridge timeout. This surfaced as brw__brw_evaluate 20003ms repeated across dozens of calls.

  • The isolation auto-open is now bounded (8s per attempt) and cooled down (15s after a failure), so a wedged browser yields one fast, logged failure instead of a per-call 20s hang. brw stays responsive and logs an actionable hint ("reload the brw extension, or pass tab_id").
  • No behavior change on a healthy browser — auto-open works as before.

Workaround on any version: pass an explicit tab_id to bypass auto-open entirely (resolves in ~30ms).

Full changelog: v0.5.0...v0.5.1

Assets 10
Loading