"WebDriver didn't wasn't quit properly" on main, but 0.35 works

[BlinkyStitt]

I have some code working with thirtyfour v0.35.

I wanted to make some modifications to the repo and so I forked main, but then my app started behaving strangely. It doesn't ever exit. When I press [ctrl+c], I detect that and call web_driver.quit().await.ok(), but on main that throws this error now:

thread 'tokio-runtime-worker' panicked at /Users/bryan/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/tokio-1.43.0/src/runtime/time/entry.rs:568:9:
A Tokio 1.x context was found, but it is being shutdown.
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I think the changes to change how drop worked have created other bugs.

I think this is the commit that breaks things: 6c67941

I reverted that in a local checkout and now the app at least exits instead of hangs. but it still does say "WebDriver didn't wasn't quit properly"

Calling quit does give an error. That is probably related:

Error: The WebDriver request returned an error: error sending request for url (http://localhost:9515/session/5062df7f7afbe1e4ee482b249635c133)

[Vrtgs]

will look into this, the new drop logic is a bit messy

[BlinkyStitt]

I think the problem might be related to having a chrome devtools object. That clones the session handle, so maybe the drop isn't running when expected?

I'll try manually dropping before calling quit.