Setup: human-review v0.6.0 (installed from a main-branch tarball), macOS 15.x, current Chrome stable. Reviewing a single local, self-contained static HTML file (~30 KB, no external requests).
Usage pattern when the crashes hit: one review target across three sessions over ~3 hours (same server port, three /s/ session URLs). The reviewer typed inline edits and left selection/element comments; meanwhile the agent saved the reviewed file 10+ times, each save triggering the live reload while the review UI held unsent state; the agent polled with human-review poll --timeout 600 throughout.
Symptom: Chrome crashed three times mid-review. No Crashpad dump was produced, so it may be renderer/tab kills rather than a full browser crash. Feedback persistence worked as documented- nothing was lost but the crash-and-reopen loop made the session unusable and we fell back to plain chat review.
Unverified suspicion: repeated save-triggered reloads while a contenteditable session holds unsent edits/comments - crashes seemed to follow several reload cycles within one session.
Happy to gather more diagnostics if you tell me what would help. Otherwise: the batch-comments workflow is genuinely good - this is the one thing that stopped me using it.
Setup: human-review v0.6.0 (installed from a main-branch tarball), macOS 15.x, current Chrome stable. Reviewing a single local, self-contained static HTML file (~30 KB, no external requests).
Usage pattern when the crashes hit: one review target across three sessions over ~3 hours (same server port, three
/s/session URLs). The reviewer typed inline edits and left selection/element comments; meanwhile the agent saved the reviewed file 10+ times, each save triggering the live reload while the review UI held unsent state; the agent polled withhuman-review poll --timeout 600throughout.Symptom: Chrome crashed three times mid-review. No Crashpad dump was produced, so it may be renderer/tab kills rather than a full browser crash. Feedback persistence worked as documented- nothing was lost but the crash-and-reopen loop made the session unusable and we fell back to plain chat review.
Unverified suspicion: repeated save-triggered reloads while a contenteditable session holds unsent edits/comments - crashes seemed to follow several reload cycles within one session.
Happy to gather more diagnostics if you tell me what would help. Otherwise: the batch-comments workflow is genuinely good - this is the one thing that stopped me using it.