Vladimir Panteleev

It looks like the exact same issue. Could you please run with `-x`, and either post the output or try to find the failing command?

Thanks. Unfortunately I can't tell what is failing from the log. Could you please try this patch (without `-x`), and post the output: https://github.com/CyberShadow/aconfmgr/compare/debug-find

> IIRC it turned out that I had a file path on my system with some odd special characters in it. The script was choking on that. Any hints for...

It's certainly possible, if GNU find is unequipped to deal with such special filesystem entries. We can test that theory - run: ```bash find / -regextype posix-extended -not '(' '('...

> I'm pretty certain GNU find can handle it just fine... I tried the find command and it ran successfully (printed `0` ) > > I tried adding all mounts...

Thanks, that's interesting! How big is `/tmp/aconfmgr-$UID/owned-files`? (or `./tmp/owned-files` if running from a checkout)

So far, unable to reproduce - grep uses a constant 631MB of RSS with 1M filter lines, no matter how much data I pipe into it. I found this report...

One possible way we can try to make progress is to reproduce it in isolation. Here's my attempt to extract the invocation in question: ```bash pacman --query --list --quiet |...

> I tried it on two other machines I have that are similarily set up, and both of them seem to be unaffected by this issue. What if you copy...

Neither tools should be doing UTF-8 decoding for case-sensitive fixed strings. I'm glad you got the problem sorted :) But, I still can't reproduce this. By any chance have you...