allocation heavy and get killed by OS

[Martinits]

Just run fd in / and it keeps allocating memory until OOM and gets killed. I often ran fd under / (actually through fzf for finding things under /). It wasn't like that before.
I'm using fd on archlinux, on a laptop with i7-8550U and 16G RAM.

❯ yay -Q fd
fd 8.4.0-1

[tavianator]

Dupe of #918 probably

[Martinits]

But fd > /dev/null gets OOM on my system too, and my system is not that big(5TB?), about 50GB I think.
The point is such situation has NEVER happened before.

[tavianator]

I'm guessing that's just due to system performance differences. Since the queue is unbounded, the worker threads can generate paths faster than the receiver thread can read them. >/dev/null speeds up the receiver thread, but not necessarily by enough.

You can try my backpressure branch. If it still OOMs then it's a different bug, otherwise it's probably the same one.

[tavianator]

It's likely that 813a802 exacerbated this by increasing the size of the objects passed through the channel.

[Martinits]

You can try my backpressure branch. If it still OOMs then it's a different bug, otherwise it's probably the same one.

Just tried this one, it's good.