-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
fix(get_window_state): 30s timeout + 2000-node cap for heavy webview apps #1609
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
Closed
hippoley
wants to merge
2
commits into
trycua:main
from
hippoley:fix/get-window-state-timeout-and-truncation
Closed
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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
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
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.
🧩 Analysis chain
🌐 Web query:
In Tokio, iftokio::time::timeoutexpires while awaiting aspawn_blockingJoinHandle, does the underlying blocking task stop, or does it continue running after the handle is dropped?💡 Result:
If
tokio::time::timeoutexpires while you’re awaiting aJoinHandlereturned bytokio::task::spawn_blocking, the underlying blocking closure does not get stopped; it continues running in the background after theJoinHandleis dropped. Tokio’s docs state thatspawn_blockingclosures “cannot be aborted because they are not async” and that even callingabort()on aspawn_blockingtask “will not have any effect” (once it has started). It also explains that when a Tokio runtime is shut down it “will attempt to abort all tasks includingspawn_blockingtasks,” but blocking tasks “cannot be aborted once they start running,” and shutdown may still wait for them to finish. [1][2] Separately, Tokio’sJoinHandlebehavior is that dropping the handle “detaches the associated task,” and “the task continues running in the background and its return value is lost.” [3][4] So, in the specific scenario you described: -timeout(...).awaittiming out typically means theawaitis dropped (i.e., theJoinHandlevariable goes out of scope / is dropped). - Dropping theJoinHandledetaches the task, so the blocking closure keeps running. - Additionally, even if you were to try to abort the handle,spawn_blockingtasks can’t be aborted once they’ve started. [1][3]Citations:
Timeout does not stop the blocking task—the AX walk continues running in the background.
When
tokio::time::timeoutexpires on thespawn_blockingJoinHandle, the underlying blocking closure is not aborted; it continues consuming a blocking thread in the pool. Repeated timeouts can accumulate idle threads and starve the blocking pool for future work.🤖 Prompt for AI Agents