grep - Bugs: bug #20286, Memory leak when searching through...
You are not allowed to post comments on this tracker with your current authentication level.
bug #20286: Memory leak when searching through big binary files
Submitter: | None | ||
Submitted: | Thu 28 Jun 2007 08:54:06 AM UTC | ||
Category: | None | Severity: | 3 - Normal |
Item Group: | None | Status: | None |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Open |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
CC list is empty
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
No changes have been made to this item
Powered by Savane 3.13-d3ae.
Corresponding source code
Memory leak shows up when searching through big binary files.
This problem can be reproduced with current CVS. Just create a big binary file and grep some string in it.
The problem was serious for me, because I was used to use "grep -r <string> ." to search through source trees. Now, this problem occoured with already compiled object and binary files.
My current workaround (which is even faster ;) is to use '-I'.
Some additional notes:
- it doesn't matter if I used '--mmap' or not.
- it seems like the memory is freed after close, because many smaller binary files (with -r) are working.
regards,
Ingo