I'm gonna narrow down this issue, because it's all related to this:
http://photolowagie.com/lowagie/render/ ... I_9421.jpg
Fatal error: Allowed memory size of 26214400 bytes exhausted (tried to allocate 7462913 bytes) in /home/photolow/public_html/lowagie/app/parsers/slir/slirimage.class.php on line 632
Let me explain to you what's going on here in steps, and why this issue is in fact a very "unlucky" coincidence.
# First of all, Imagevue loads resized images based on math and algorithms to best suit the specific layout- and device that it is being viewed from. That is why you will see
/render/ path for many images, as the original
/content/ is considered max size.
#
Why it works here? For example, from here on my macbook 13" retina, it loads a smaller image, which works fine.
http://photolowagie.com/lowagie/render/ ... I_9421.jpg
# Your original image is
1068 px wide. That is still bigger than the "estimated" size
1024px it wants to load for your specific screen (I assume a large LCD). Therefore, it tries to load the resized image ... If your original image was 1024px wide (or smaller), it would load the original image without resizing, and there would not be any errors.
#
Why does it work with the other portraits? Your "other" portraits just happen to not be as extreme aspect as this specific image. The other images that work, request a smaller height in the resize than the image that creates the error. This also proves that it is likely that your server is just a very few % short on memory to be able to render the image that creates the error.
#
But why the error though? This is because this specific image has an incredibly unconventional aspect ratio, and your server simply doesn't have the memory to handle resizing to
1024 x 1822 px (which is a very large "height" value).
For example, the other portraits are requesting
1024 x 1534px, as you can see a smaller size.
# Conclusion, this issue only happens specifically when
1) Your server has limited memory resources (although that is normal),
2) Only when being viewed from a large monitor where the "max" 1024 width is calculated (as in your case),
3) Only for such a specific ultra-tall aspect ratio (if it was for instance 2:3 aspect, it would not have problems loading 1024 x 1536).
4) Because essentially, this ultra-tall aspect ratio is creating a bigger image than your server (and therefore Imagevue) is able to process properly.
Solution
I am not sure how your resizing workflow is, but essentially the image
width of such aspect is too large. When resizing images with such aspects, the problem would be solved if you had a max-width of
1024 px. If you have 1024px width instead of 1068px, the X3-resizer would not need to kick in when requesting the 1024px size, and it would show the original instead.
For images of normal aspect ratios like 3:2 or 2:3 (or even your other portrait aspects), you need not worry about anything. They will resize nicely because they won't get out-of-proportion resize requests based on extreme aspects.