retitle 675212 cannot control max memory when using -progressive thanks On Wed, May 30, 2012 at 6:19 PM, Mathieu Malaterre <[email protected]> wrote: > On Wed, May 30, 2012 at 5:43 PM, Bill Allombert > <[email protected]> wrote: >> Please look at the manpage. There is both an environment variable JPEGMEM >> and a >> flag -maxmemory to limit the memory usage. This is a benefit of libjpeg8 >> over >> libjpeg62. > > 1. here is what man page states: > ... > -maxmemory N > Set limit for amount of memory to use in processing > large images. Value is in thousands of bytes, or millions of bytes if > "M" is attached > to the number. For example, -max 4m selects 4000000 > bytes. If more space is needed, temporary files will be used. > ... > > I believe "-max 4m" is wrong here and should read "-maxmemory 4m". > > 2. I have been using xosview and top to check memory consumption but > the flag and the env var are never used in my case: > > $ export JPEGMEM=4000 > $ cjpeg -maxmemory 4M -progressive -arithmetic -rgb -block 1 -outfile > huge1.jpg -quality 100 huge.ppm > > xosview shows ~4Gb of RAM used before I kill the process
Answering to myself just removing the command line option '-progressive' did the trick. So -progressive and -maxmemory are mutually exclusive. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
