When searching for string (no regex etc.) in large file less filename and less -b 1 filename quits or prints it cannot allocate memory. top shows less using roughly about 5% of memory before it dies (1 sec interval).What other tool can I use that supports large files? The file has only 100 mb of logs.$ less -Vless 458 (GNU regular expressions)Copyright (C) 1984-2012 Mark NudelmanOS details:$ ulimit -a-t: cpu time (seconds)              unlimited-f: file size (blocks)              unlimited-d: data seg size (kbytes)          unlimited-s: stack size (kbytes)             8192-c: core file size (blocks)         0-m: resident set size (kbytes)      unlimited-u: processes                       15988-n: file descriptors                1024-l: locked-in-memory size (kbytes)  64-v: address space (kbytes)          2048000-x: file locks                      unlimited-i: pending signals                 15988-q: bytes in POSIX msg queues       819200-e: max nice                        0-r: max rt priority                 0-N 15:                              unlimited$ cat /etc/*rele*DISTRIB_ID=UbuntuDISTRIB_RELEASE=13.10
less command runs out of memory
less;gnu
This probably has nothing to do with your memory and everything to do with the way less is written and how much space it allocates for it's internal variables.Anyway, less is really not designed for this, you should use a tool like grep instead:grep yourQuery fileIf you want to see the lines around your query (5 for example), run this:grep -C 5 yourQuery fileIf you have too many matches for that, you can pass the output to less and now you should be able to search through it:grep -C 5 yourQuery file | lessOf course, if you want to do this manually, you can open the file in a text editor. Any serious editor like vim or emacs will be able to open and search through a 100MB file.