Repository navigation
worker: stop the start sequence when a handler it calls stops the worker #44486
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
robobun
wants to merge
3
commits into
main
Choose a base branch
from
robobun/0eb29a2b/worker-start-stand-down
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 nit (optional): on a release build, deleting the new check at src/jsc/web_worker.rs:888 breaks no test, so a release-only CI lane cannot catch its regression. The two 'workerMessage' rows here print "exit 7" / "exit 1" with or without that check; only debug and ASAN builds abort, and the single row that differs on release (getHeapSnapshot) exercises the observe_entry clause, not this one. Fix: make each load-bearing clause fail a test on every build, e.g. add a 'workerMessage' row whose parent also holds a pending worker.getHeapSnapshot() and expects "snapshot rejected ERR_WORKER_NOT_RUNNING", since without the check the worker still reaches Running and the snapshot resolves.
Why this was flagged
Without the check at src/jsc/web_worker.rs:888 on a release build, the 'workerMessage' process.exit(7) row runs: WebWorker__entrySettled runs the listener, process.exit(7) sets exit_code and requests termination, observe_entry at web_worker.rs:923 sees a fulfilled entry promise and returns Continue, WebWorker__workerGlobalScopeStarted at web_worker.rs:939 moves the proxy to Running, run_gc at web_worker.rs:949 does not assert on release, the loop breaks at web_worker.rs:959 and shutdown reports exit 7. The row's expected lines are identical, so the test passes both ways on release; the getHeapSnapshot row only covers the observe_entry change at web_worker.rs:916. REVIEW.md asks that deleting each load-bearing clause of the fix break at least one test. A pending getHeapSnapshot() in the 'workerMessage' rows would distinguish: with the check the proxy never reaches Running and rejectAllCrossVMRequests (WorkerMessagingProxy.cpp:564) rejects it; without it the pending task runs after workerGlobalScopeStarted and resolves.
Verification: Without the new check at src/jsc/web_worker.rs:888-891, the two 'workerMessage' rows take observe_entry line 902 -> Continue, run_gc line 949 (the ASSERT in VMTraps.cpp is compiled out in release), then the loop at 957-961 breaks and shutdown() runs with exit_code already 7. Stdout is "exit 7"/"exit 1", exactly what the test at test/js/node/worker_threads/worker_threads.test.ts:775 expects.