Questions and postings pertaining to the usage of ImageMagick regardless of the interface. This includes the command-line utilities, as well as the C and C++ APIs. Usage questions are like "How do I use ImageMagick to create drop shadows?".
If you delete, or comment-out, all those settings then you won't hit any limits.
Personally, that's what I do (on my personal computer, not a server). You may prefer to be more conservative, eg allow IM to use only half your memory.
I think IM failed to process some of those .tiff files.
Interestingly, I have set no restrictions in the policy map and turned off memory allocation in my bash script and '-alpha off' fails with convert and mogrify.
mogrify -alpha off *.tiff
or
for f in `ls -v *.tiff`; do mogrify -alpha off $f; done
both throw memory allocation errors while not performing the command, which can be seen when the image alignment script reports 'treating associated alpha as unassociated alpha,
Have you tried just processing one file with magick. For IM 7, you need to use magick rather than convert and magick mogrify rather than mogrify. See https://imagemagick.org/script/porting.php#cli
Unfortunately, xubuntu ships with <IM7 so all convert at the moment. No previous problems with IM until update to xubuntu 18+ so not sure why the difference. Fortunately, the mogrify step is not essential, but worth noting in view of the error messages.
TIFF* TIFF rw+ Tagged Image File Format (LIBTIFF, Version 4.0.9)
TIFF64* TIFF rw- Tagged Image File Format (64-bit) (LIBTIFF, Version 4.0.9)
Playing around with policymap values, mogrify was erratic and eventually complained about memory after several files. With policymap commented out, the first or second file would be OK and the remainder throw errors.
So what version and date is associated with your xUbuntux? Can you post an example TIFF that fails to some free hosting service such as dropbox.com that won't change the format (or zip it first)