-
-
Notifications
You must be signed in to change notification settings - Fork 147
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
Finished tasks sometimes stay in the console and appear busy #189
Comments
@daladim that would be super useful! |
Is it possible that these tasks have completed, but have not yet been dropped? Are the |
I think I was able to reproduce something similar, if you run the following example for ~2 minutes or so with the latest commit I start to see the idle task count continually increasing. Theoretically this code should be dropping all of the task handles correctly.
|
@colinjfw interesting, thanks for the repro! |
Thanks for doing what I did not have to time do lately :-) |
That's much better now, I no longer see this bug. Thanks for your work! I'm closing the issue. |
Great, thank you! |
Thanks for this great tool, that I'm using to have insights on a large app that spawns many tasks.
When I run the console long enough, it eventually displays busy tasks that run forever.
However, I'm quite positive all these tasks are finished. Indeed, these tasks are spawned via
and they all have reached the last line of
some_async_function
, where I added aprintln!("Finished task {}", some_task_id)
that actually got displayed.So that looks either like a tokio bug that did not joined the task after it reached its last line, or a bug in the console-subscriber that misses some "task is finished" events (or in tokio-console that does not process them).
Ideas to create a minimal reproducer
Have a function that spams tasks, that all complete after some time (let's say after a random (sync or async) sleep between 1 and 40s).
I could try to write it myself if that could be helpful to you.
I am building and running on Win10 if that matters
The text was updated successfully, but these errors were encountered: