Scaled image file write failed

[kapeskp]

Scaling to 4x completes properly. Any further scaling fails at the file write stage. Log says "BACKEND REPORTED: File Operation Cancelled". What could be the issue? I have sufficient space in disc

[dosubot[bot]]

Hey there, @kapeskp! I'm here to help you with any bugs, questions, or contributions you have. Let's tackle this issue together!

The "BACKEND REPORTED: File Operation Cancelled" error could be due to a read/write error, possibly related to file permissions or access issues, rather than disk space. Ensure that Upscayl has the necessary permissions to write files, especially if you're using a Flatpak version, which requires --filesystem=home permission to access the home directory ^[1]. Additionally, check if the filename length exceeds the maximum path length allowed by Windows, as this can also cause issues ^[2].

To continue talking to Dosu, mention @dosu.

[kapeskp]

I don't think it is permissions. Upscayl was able to write a 4x scaled file twice. I tried with a shorter file name and that did not write out either. Although log was different this time. I notice that my disc is consumed by around thee size of the output file every time I try a failed upscale. Is it possible file is being written in a different location? Or it could be temp files being created while image is being generated.
Is there an image size restriction? Output image resolution requested is 22144x10112.

[dosubot[bot]]

There isn't a specific image size restriction documented in Upscayl, but large image resolutions can cause issues, especially if the output file path length exceeds 255 characters on Windows ^[1].

Regarding temporary files, I couldn't find specific information on where Upscayl stores them or if they are automatically deleted after processing. It's possible that temporary files are consuming disk space during the upscale process. You might want to check your system's temporary file directories to see if they are being stored there.

To continue talking to Dosu, mention @dosu.

[kapeskp]

Looks like it is the image resolution. If I split the image into smaller piece it successfully writes the scaled image.

[kapeskp]

It might also be the file size since file size was reduced accordingly. But I had tried to save it in WEBP format which should have helped with file size. So very likely image resolution of the scaled image

[auswade]

I have the same problem, happens on all files when I try to increase the upscale more than 4x

[aaronliu0130]

I think this is the same thing as #493.