'ls' in nu hangs with 100% CPU on a directory with ~4000 files (doesn't finish in 5+ minutes)

[yurivict]

Describe the bug

I've ran 'ls' on a /tmp directory on a large server with an assortment of temporary files left by all sorts of processes.
It didn't finish in 5 minutes.

The command 'ls -l' on the same directory finishes in several seconds.

How to reproduce

See above.

Expected behavior

See above.

Screenshots

No response

Configuration

n/a

Additional context

No response

[fdncred]

without a way to reproduce, this will be very difficult to troubleshoot. even though, this reminds me that it would be nice to have the ls command be multithreaded.

[yurivict]

There should be a way to profile a Rust application.
Maybe it's possible to reduce this case to a smaller file set and print profile info?
But I am not familiar with Rust enough to know how to do this.