memory allocation of 2147483648 bytes failed (that's 2GB!) about suckit HOT 5 OPEN

Thanks a lot for the report. We're investigating it

from suckit.

cargo install does strip debug symbols since it's building in release mode. You can compile the project with cargo build if you want them, or simply run cargo run -- <your suckit arguments>. Thanks again, I'll let you know how we're progressing.

from suckit.

Ah actually I do have one other bit of information, because my .zshrc outputs timing for any command over 2 seconds:

25:52.17s total, 130.18s user, 196.37s system, 21% cpu

from suckit.

I can see from re-running with --versbose that it ascended to a parent directory so I suppose it may have encountered a larger file or has some data structure that is growing with each link and hit some upper bound.

from suckit.

Re-running reproduced it at the ~28 minute mark. No backtrace shown even with RUST_BACKTRACE=1 (haven't tried RUST_BACKTRACE=full), but I haven't checked if cargo install strips debug symbols or something. Hopefully you're able to reproduce.

from suckit.