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.
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
fix: Fix hung launcher on shutdown of Safari #38
fix: Fix hung launcher on shutdown of Safari #38
Changes from all commits
43be149
b010b4f
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Say, what's the difference between the
kill
andforceKill
operations? They both just callstopWebdriver_
.Is
kill
called in such a way that we don't need to worry about them being nested, or about aforceKIll
being nested inside akill
?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.
kill() and forceKill() are part of the launcher API, but in my logs, I don't see kill() being called. In a purely external-process-based launcher, the base classes would send different POSIX signals to the subprocess for kill() and forceKill() if I recall correctly.
I initially thought forceKill() should never fail or be infinitely delayed, so I tried adding a timeout at the level of forceKill(). But that didn't solve the issue. In the end, I added the timeout to the WebDriver quit command, since that's the only thing that can fail or be delayed.
So after all the debugging and logging, I concluded that kill() and forceKill() can still effectively be the same, except for the state tracking part.
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.
I see. I was going to suggest moving the new logic for saving the operation as a promise into
stopWebdriver_
, instead offorceKill
. But ifkill
isn't being called I guess it doesn't matter.