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
sharded-slab panic after upgrade to tokio 1.9.0 (and other crates) #1485
Comments
Thanks for the report! Interestingly, I notice that none of the tracing-related dependencies changed in the update. My suspicion is that something that changed in Tokio 1.9 is breaking |
@jeromegn a couple questions: is your code spawning a very large number of threads? are you using Tokio's blocking pool? |
the panic at that location suggests that you have 4134 threads currently active (or that thread IDs are not being correctly reused?) |
If you can, try |
Per a Discord conversation, it seems like @jeromegn's app spawns a lot of threads (separate Tokio runtimes). Normally, the app doesn't have more than 200 threads concurrently alive, which shouldn't hit the 4096 thread limit in the Right now, it seems like the best solution here is:
I do think I'm closing this issue since there's not really anything to fix in |
FWIW that won't work as all threads get thread ids from single |
Adds CollectionBuilder with_slab_config::<S>() func to this end. This e.g. allows to use tracing in environment with >= 4k threads. c.f. tokio-rs#1485
Adds CollectionBuilder with_slab_config::<S>() func to this end. This e.g. allows to use tracing in environment with >= 4k threads. c.f. tokio-rs#1485
Bug Report
Version
Platform
Linux kernel 5.11.7, Ubuntu Bionic
Crates
I believe this is happening in
tracing-subscriber
Description
We routinely upgrade dependencies on our rust-based proxy. This time it seemed to cause a lot of panics when we rolled it out.
It appeared to happen when create spans. I'm not entirely sure.
Example line where a panic occurred:
(it seems to happen all over the place)
Here's the panic:
Here's the list of upgraded depencies:
The text was updated successfully, but these errors were encountered: