Skip to content
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

Runasync causing deadlock? #146

Open
skyhirider opened this issue Feb 7, 2024 · 0 comments
Open

Runasync causing deadlock? #146

skyhirider opened this issue Feb 7, 2024 · 0 comments

Comments

@skyhirider
Copy link

When running the driver, I was able to deadlock it by calling driver.get(url) while the runAsyncRunning_ was already set to true.

The driver ended up in an endless loop and whatever originally set the field to true never finished (or was interrupted).

I'm wondering what the reason is to wait for async when calling driver.get, as ideally I would expect the driver to drop everything it was doing (and ignore any background javascript or other async tasks) and immediately open the new page.

Or is this standard behavior on other browsers as well where opening a new url in the same window is delayed until background tasks finish?

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

No branches or pull requests

1 participant