Roberto,
you can fix the maximum read size with the -r parameter on the command
line. By default, recoverjpeg uses 128M of memory. Try to run it with
-r 32M to use 32M of RAM.
recoverjpeg doesn't leak memory. It does only one single malloc() in
main(), not in a loop, and no function is ever
Samuel Tardieu wrote:
you can fix the maximum read size with the -r parameter on the command
line. By default, recoverjpeg uses 128M of memory. Try to run it with
-r 32M to use 32M of RAM.
recoverjpeg doesn't leak memory. It does only one single malloc() in
main(), not in a loop, and no
Package: recoverjpeg
Version: 1.1.1-1
recoverjpeg seems to use too much memory on a big hard drive. Making the
process too slow as it has to use swap.
Maybe valgrind should be run on it to detect memory leaks and it should
use mmap when possible.
Prueba el Nuevo Correo Terra; Seguro, R�pido,
3 matches
Mail list logo
