Chrome is cool but have you ever assembled a 96 megapixel png with magick?
That shit uses 3GB ram why
At least now that I reserved a third of my memory to the linux VM my hard drive isn't abused for its page file anymore

  • 3
    96MP at rgba becomes 384MB. If you're on the 16b per component, then 768MB minimum. To get to 3GB then it would need to work with 4copies of the same image. Possible? Maybe, I am not super familiar with the internals.
  • 0
    @jespersh that's what I thought but I barely understand what I'm doing.

    Took me a quite a while to figure out the commands to do what I want. I don't think there should be more than copies in memory at one time.
  • 2
    @Conrad Imagemagick needs to allocate a few things and pulls everything into memory in order to be faster.

    Meaning the full size of your output image has to be allocated. The images you are stitching together and each of them twice as you specified the -clone 0 flag.
    I'm currently not sure if your resize operation will also allocate another buffer though.

    This will quickly add up.
Add Comment