Closed zicklag closed 1 year ago
It's especially surprising that loom types appear in this call stack? IIRC you have to opt in to that with RUSTFLAGS?
Oh, and in case it helps, here's my Cargo.toml dependency. I'm using the master release right now.
quinn = { git = "https://github.com/quinn-rs/quinn.git", default-features = false, features = ["futures-io", "native-certs", "tls-rustls"] }
I haven't ( intentionally ) tweaked the RUSTFLAGS at all, and I don't know much about loom.
Unless some tokio synchronization primitives are still used even when not using the runtime, which could make sense.
This is the case. Notify
is a really handy unopinionated primitive. This issue should probably be raised upstream with them.
Opened an issue in Tokio: https://github.com/tokio-rs/tokio/issues/5122.
Going to close this for now, assuming there is no further work on our side.
I was trying to protect my app from unexpected crashes by catching panics using
catch_unwind
, butConnection
isn't unwind safe. Do you think it's possible to make unwind safe?Also, I disabled the default features and haven't enabled
runtime-tokio
, so I'm not sure why it's pulling intokio
types. Unless sometokio
synchronization primitives are still used even when not using the runtime, which could make sense.