Closed ropery closed 7 years ago
What image and arguments did you run with?
I ran this in a batch job; didn't really catch the image being processed that generated this error.
These are small images downloaded then passed to primitive
. Of the hundreds of images, on which the same arguments are used, this is the one single image that produced this error.
Since randomness is involved, I thought it might just be an edge case of 0
.
Edit: OK I checked my "backlog" and it's a dummy JPEG of size 1x1
JPEG 1x1 1x1+0+0 8-bit Gray 256c 160B 0.000u 0:00.000
Running primitive
on it thousands times over has not reproduced the panic. Very strange.
I doubt anyone else has encountered this. Feel free to close the issue.
I suspected a tiny image. I think some other code changes fixed it anyway.
Looks like
0
is passed toIntn
?