You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to a issue in our application (tramhao/termusic#603) i recommended to use tokio-console to debug this, but somehow one task on windows is always listed as 1 tasks have lost their wakers, even though the task has exited successfully.
I seemingly cannot reproduce this on linux, but 100% on windows. On windows tokio-console shows that task as IDLE with time increasing - even on re-connect.
Output looks about like this:
This originally let me to believe this "stuck task" was the issue on why our application seemingly did not exit correctly (which let me to believe tokio was not exiting (which is somehow still true), but it being this task turned out to be wrong, as actually testing the (discarded handle) handle.is_finished() it returned true).
Does anyone know why this happens on windows and maybe how to fix it?
Kinda unrelated to the discussion above, but it turns out that the issue preventing our application from closing is tokio, as it is seemingly stuck on some BUSY(with time increasing) tokio/src/io/blocking:76:46 tasks.
The only relevant field tokio-console reports is fn=<tokio::io::blocking::Blocking<tokio::process::imp::ArcFile> as tokio::io::async_read::AsyncRead>::poll_read::{{closure}}.
Doing a skim in the tokio repo, i found this it only uses ArcFile for ChildStdio on windows, so i guess it is related to this task, as those somehow never exit. Is this is a tokio implementation issue, or a windows API being different and blocking issue? tokio1.48.0
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Due to a issue in our application (tramhao/termusic#603) i recommended to use
tokio-consoleto debug this, but somehow one task on windows is always listed as1 tasks have lost their wakers, even though the task has exited successfully.I seemingly cannot reproduce this on linux, but 100% on windows. On windows
tokio-consoleshows that task asIDLEwith time increasing - even on re-connect.Output looks about like this:

This originally let me to believe this "stuck task" was the issue on why our application seemingly did not exit correctly (which let me to believe tokio was not exiting (which is somehow still true), but it being this task turned out to be wrong, as actually testing the (discarded handle)
handle.is_finished()it returnedtrue).Does anyone know why this happens on windows and maybe how to fix it?
The task in question:
https://github.com/tramhao/termusic/blob/b1fa82f42435b206a977abd1f399285b489f405c/tui/src/main.rs#L164-L184
(or for convenience, copy-pasted:)
Kinda unrelated to the discussion above, but it turns out that the issue preventing our application from closing is tokio, as it is seemingly stuck on some
BUSY(with time increasing)tokio/src/io/blocking:76:46tasks.The only relevant field
tokio-consolereports isfn=<tokio::io::blocking::Blocking<tokio::process::imp::ArcFile> as tokio::io::async_read::AsyncRead>::poll_read::{{closure}}.Doing a skim in the tokio repo, i found this it only uses
ArcFilefor ChildStdio on windows, so i guess it is related to this task, as those somehow never exit. Is this is a tokio implementation issue, or a windows API being different and blocking issue?tokio1.48.0Beta Was this translation helpful? Give feedback.
All reactions