mirror of
https://github.com/narrrl/proton-drive-linux.git
synced 2026-11-04 08:56:59 +01:00
nvrl
cf0d495f8c
Teardown flagged the FUSE worker pool closed but never joined it, so the process could drop the tokio runtime while a worker was still inside a job — which is where 2026-09-18's "A Tokio 1.x context was found, but it is being shutdown" panic came from. `Workers::stop_and_join` now waits for the jobs in flight, bounded at 10 s so a worker wedged on the network cannot hold the stop the user asked for; what is still stuck is named in the log and shutdown continues around it. The queues stay unbounded — the only caller that could feel backpressure is fuser's dispatch loop, and blocking that is the stall the pool exists to avoid — but a lane now logs its depth every 256 jobs, so a queue that keeps climbing is visible before it is reported as a slow mount. Documents the hang as B91, with the journal evidence, what made it undiagnosable, and the candidates the evidence does not yet separate.