Legacy ImageMagick Discussions Archive

I'm running a script to create a 2px by 2px png file for each of the possible 16.7 million colors available in the hex color spectrum. Here's the script:
newhexcodes.txt contains a list of all possible hex colors. Please don't ask why I have to do this instead of auto generating the images at run time. Suffice it to say, I just do. I know that it's very kludgey.

Things begin nicely. I've created a virtual machine with CentOS 6.4 and allocated 1.5 gig of RAM to it. At some point, I get this error:

convert: unable to open image `268611.png': No space left on device @ blob.c/OpenBlob/2480.

There is ample disk space for this. Calculating 16.7 million X 222 bytes per image = ~4.175 GIG. The script fails with more than 19 GIG of disk space still open.

Does IM try to keep all of the process in memory? Is there another cause for this kind of error?

Check your /tmp partition. Its running out of disk space. Use the MAGICK_TMPDIR environment variable to point ImageMagick to a different partition for free space. Add -debug cache to the command line to track the temporary file resource requirements.

Thanks for the quick reply! I saw that it's possible to do this with:
Do I use this in a general terminal session or do I need to declare this in the script itself?

Add it to your script. Make sure you have permissions to write to the partition.

Getting this error:
The script currently reads: Is the putenv statement out of place?

In a shell script, its

• export MAGICK_TMPDIR=/home/smcgown/PNGS

Thank you very much. That worked perfectly.