-
Notifications
You must be signed in to change notification settings - Fork 497
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
[Bug]: panic during shutdown with TokioCurrentThread batch tracer #1963
Comments
Note: we don't use the multi-threaded runtime due to #868. Ill do some more investigation into if that has been resolved though, as that is a bit stale |
I believe the root cause here is we build a ticker tied to the outer runtime: let ticker = runtime
.interval(config.scheduled_delay)
.map(|_| BatchMessage::Flush(None)); This timer actually refers to the outer runtime, but we poll it from a different runtime. I will attempt a fix |
@howardjohn Thanks for reporting the issue along with a clean repro and the fix! Really appreciate it. One thing - you should still call shutdown() at the end to ensure telemetry is flushed out |
What happened?
Cargo.toml:
main.rs:
RUST_BACKTRACE doesn't work for this crash for some reason, not sure why. If you run in a debugger you can see the stack:
API Version
0.24.0
SDK Version
0.24.1
What Exporter(s) are you seeing the problem on?
No response
Relevant log output
thread '<unnamed>' panicked at /home/john/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.39.1/src/runtime/time/entry.rs:568:9: A Tokio 1.x context was found, but it is being shutdown.
The text was updated successfully, but these errors were encountered: