-
Notifications
You must be signed in to change notification settings - Fork 194
panic during shutdown with RUST_LOG=trace #1904
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
Comments
This is probably due logging during CLEANUP without threadlocal environment |
Hi @alokpr, we have been aware of this thread local storage issue and don't suggest any shutdown during this stage. Unfortunately, I can't reproduce your problem using the steps below. export RUST_LOG="trace"
# Use rust-toolchain 1.86.0
cargo run --bin zenohd
# Press Ctrl-C to terminate I noticed that you have the shared memory feature enabled in the log. Can you show us the detailed steps to reproduce this issue? |
What do you mean by you "don't suggest any shutdown"? The panic happens automatically during process shutdown due to the usage of static_init::dynamic::drop here - zenoh/commons/zenoh-shm/src/cleanup.rs Line 24 in 037c546
I will get you repro steps. |
Hi @alokpr! I mean we don't suggest any shutdown of the async runtime during the exit stage or any similarly causing TLS issue. And I understand that this time is probably caused by our shared memory cleanup. We are happy to resolve this if you can provide some steps to reproduce it. |
@YuanYuYuan Thanks for the quick response. It is a bit hard to test unreleased crates in our dev setup right now. I will see if I can repro the issue outside our project and test #1907 |
Describe the bug
With "trace" log-level, zenoh panics with the following callstack:
To reproduce
System info
The text was updated successfully, but these errors were encountered: