Scanning stucks on macOS 14.0 about dua-cli HOT 6 CLOSED

It's strange and I have not encountered that before. You could try different command-line flags to alter if it crosses filesystems. Threads could be changed so only a single thread is used, and when that gets stuck the activity monitor can show opened files - maybe that shows what blocks it.

In general, dua can only get stuck if the filesystem blocks forever/a long time when getting file metadata.

from dua-cli.

Hi, I tried dua -t 1 i and saw it get stuck at .orbstack. Then I tried dua -t 1 -i .orbstack i and saw it get stuck at .cargo... Then dua -t 1 -i .orbstack -i .cargo i and it still get stucks...

from dua-cli.

Interesting - both work for me.

What do other tools do? I'd expect them to get stuck as well.

from dua-cli.

Hi, I tried dust, erdtree and GUI tools like DaisyDisk.app, all work fine.

from dua-cli.

That's really interesting - dua does't do anything special, just symlink_metadata() calls on paths. With -t multi-threading goes away as well so that can't be a source of deadlocking either. I assume this truly is 'blocking' behaviour, right? That is, there is no high-CPU observable?

from dua-cli.

That is, there is no high-CPU observable?

Yes.

I reinstall everything (dua, rust etc.) and reboot many times... And the issue is now gone. Not sure what was happened...I'm going to close the issue now. Thanks for your help!

from dua-cli.