VIPS_MAX_COORD prevents `join`/`insert` operations with obscure messages about libvips HOT 5 CLOSED

Heh OK, let's bump it to 100m and add a config option. I made a quick PR, let's continue any discussion there.

from libvips.

It's an API change, so it'll be in 8.16, out some time this summer I guess.

from libvips.

Hi @AKlaus,

Wow I must say I never imagined 10m pixels would be too few. I may have said something similar before, of course ...

I think it's a good idea to have a "beyond this, something has broken" limit, but of course we'd be happy to raise the current bar. Do you have a feeling for what a sensible upper bound might be? I guess the practical limit would be 2bn.

It could also be set via an environment variable I suppose, eg. VIPS_MAX_COORD.

from libvips.

Thank you for understanding.
For our case, we don't expect images beyond 30,000,000px in height.
But again, as the famous saying "640KB of memory ought to be enough for anybody" goes, there's a chance of hitting the ceiling in 5 years but that's beyond my horizon :).

from libvips.

We appreciate your help.
Is the next version (v8.15.2?) going to be released anytime soon?

from libvips.