Generation size is still slightly different from selection size

[R4rum]

Describe the bug
I think these two lines of log speak for themselves:
auto-sd-paint-ext:INFO: img size: 1374x1054 -> 1374x1054, aspect ratio: 1.30 -> 1.30, 0.00% change
auto-sd-paint-ext:INFO: img Size: 1368x1048, target: 1374x1054

That latter one is from after the generation. Note how the size has changed.

Desktop (please complete the following information):

• OS: Linux
• WebUI commit revision 226d840e84c5f306350b0681945989b86760e616
• Extension commit revision 2358931

[RainehDaze]

The new img size is under your max size and it's generating a larger image then downscaling, I think.

[R4rum]

This result of mine was gotten with the Disable base/max size checked. Probably it's easier to get that weirdness to happen like that but I would imagine it's not impossible with the base/max size system either; I feel like it's happened even then.

[RainehDaze]

Looking at the numbers, it might be that your image dimensions have to be divisible by 8 and it rounded down to the nearest size it can generate.

[R4rum]

I think you are right. I looked at a whole bunch of resolutions it generates at, and they all came out divisible by 8.

It seems we come back to this comment, then, since some striding is still needed apparently. #113 (comment)

[Interpause]

I wonder if there is somewhere inside the webUI code were the stride value is stored.