Skip to content

fix: prevent stopped event buses from restarting a busy loop - #39

Open
zwk110 wants to merge 3 commits into
browser-use:mainfrom
zwk110:codex/stop-shutdown-eventbus-loops
Open

zwk110 wants to merge 3 commits into
browser-use:mainfrom
zwk110:codex/stop-shutdown-eventbus-loops

Conversation

@zwk110

@zwk110 zwk110 commented Oct 21, 2026 •

Copy link
Copy Markdown

Fixes #38.

A late dispatch still raises QueueShutDown, but _start() rejects the shut-down queue before creating another run loop. Shutdown and cancellation reach the loop's existing exit handlers, and the temporary queue-get task is always cleaned up.

Idle waits return after stop without restarting the bus, including waits already in progress. They use the existing idle signal, which the run loop sets after draining work and stop() sets when aborting it. The queue and event state are checked again before returning while the bus is running.

Reproduced the report's stop/dispatch sequence on Windows with Python 3.12: the original process stayed running after cancellation and used about one CPU core; the fixed version stays stopped and exits normally. Also reproduced a pending idle wait hanging during immediate stop on both the unchanged upstream base and the earlier PR head; it now returns.

Validation: nine shutdown/idle-wait cases pass, including a normal wait that must not return before its handler finishes. The full suite passes (147 tests, one existing duplicate-handler warning), as do the repository's pre-commit checks. The initial four shutdown regressions failed on the unchanged upstream base; two concurrent-stop regression cases failed on the previous PR head.

@cubic-dev-ai cubic-dev-ai Bot left a comment •

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All reported issues were addressed across 2 files

Reply with feedback, questions, or to request a fix.

View guided diff | Re-trigger cubic

Comment thread bubus/service.py
Comment thread tests/test_shutdown.py

@cubic-dev-ai cubic-dev-ai Bot left a comment •

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All reported issues were addressed across 3 files (changes from recent commits).

Reply with feedback, questions, or to request a fix.

View guided diff | Re-trigger cubic

Comment thread bubus/service.py
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Dispatch after stop() restarts _run_loop on the shut-down queue and spins a CPU core forever

1 participant