Skip to content

Runasync causing deadlock? #146

Open
@skyhirider

Description

@skyhirider

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?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions