- Original Message -
> Thanks for reporting that. I can't reproduce the bug here but I think I
> see why it's happening; grep is working but the test case is incorrect
> on some platforms. I installed the attached patch and am boldly marking
> the bug as fixed. (I see now that the commit's
Using the files [1], [2] (around 1.4 MB each) and running the
following command:
$ grep -v -f file1 file2
quickly consumes all of my memory (16 GB) and exits with memory
exhausted error. I have reports that it behave the same on machine
with 180 GB RAM. Well, -F should be used as there are no reg
