-define jpeg:extent appears to be using binary search to locate the optimum quality value in the range of 100 integers, and thus should do so in at most log_2(100)≈7 iterations.
According to -monitor, it frequently produces more than 7 temporary images while working.
Why would more than 7 temporary images ever (i.e. under any circumstances) need to be tested in order to locate the required quality value?
-define jpeg:extent binary search iterations
Re: -define jpeg:extent binary search iterations
We can reproduce the problem you posted and have a patch in ImageMagick 6.8.4-10 Beta available by sometime tomorrow. Thanks.