Lightroom 3.3 still have big Memory leak problem in size ...
Posted: Fri Dec 10, 2010 4:01 am
Well ... After waiting for the fix to include the EXIF properly with the Force File Size option in JPEG export, I just experienced tonight that the problem of the Memory leak ... or more Looping program problem is still there.
Here is a example on how far the software can go ...
, So Lightroom will not even create an error in batch export, but just skip all the image without giving you any warning. So I recommend that if you want to enforce File size for the moment to do it picture by picture.
This is example when you set large File size restriction (that at least linked to not force anymore
, better to use % compression)
And ... the problem of the EXIF is still there if there is picture that have been generated successfully in batch and if the File Size has gone in loop.
I'm writing this just for people like me that don't want after importing group of picture in Pbase to realized that the EXIF is not there and you have to wait again for the big ZIP to be import.
Regards,
Frank
Here is a example on how far the software can go ...
, So Lightroom will not even create an error in batch export, but just skip all the image without giving you any warning. So I recommend that if you want to enforce File size for the moment to do it picture by picture.
This is example when you set large File size restriction (that at least linked to not force anymore
, better to use % compression)And ... the problem of the EXIF is still there if there is picture that have been generated successfully in batch and if the File Size has gone in loop.
I'm writing this just for people like me that don't want after importing group of picture in Pbase to realized that the EXIF is not there and you have to wait again for the big ZIP to be import.
Regards,
Frank