[BUG][MEMORY LIMIT] Upscayl fails when upscaling large image #493

stevehorwitz · 2023-09-25T22:34:44Z

Checklist

I have checked that this issue isn't addressed in the FAQ.
I have checked that this issue isn't addressed in any other issue or pull request.
I have tried setting my GPU ID.

Paste the logs

⚙️ Getting saveImageAs from localStorage:  jpg
⚙️ Getting model from localStorage:  {"label":"General Photo (Ultrasharp)","value":"ultrasharp"}
⚙️ Getting gpuId from localStorage:  0
🔀 Setting model to 
🔄 Resetting image paths
🐞 BACKEND REPORTED:  💾 Updating Save Output Folder:  false
🔀 Setting model to ultrasharp
🐞 BACKEND REPORTED:  📝 Updating Overwrite:  false
🔄 Resetting image paths
🐞 BACKEND REPORTED:  🖼️ Updating Image Path:  C:\Projects\Greece2023\Aphrodite statue on Milos.jpg
🐞 BACKEND REPORTED:  📄 Selected File Path:  C:\Projects\Greece2023\Aphrodite statue on Milos.jpg
🖼 Selected Image Path:  C:\Projects\Greece2023\Aphrodite statue on Milos.jpg
📁 Selected Image Directory:  C:\Projects\Greece2023
🖼 imagePath:  C:\Projects\Greece2023\Aphrodite statue on Milos.jpg
🔤 Extension:  jpg
🔄 Resetting Upscaled Image Path
🏁 UPSCAYL
🐞 BACKEND REPORTED:  📝 Updating Overwrite:  false
🐞 BACKEND REPORTED:  ✅ Upscayl Variables:  [object Object]
🐞 BACKEND REPORTED:  📢 Upscayl Command:  -i,C:\Projects\Greece2023\Aphrodite statue on Milos.jpg,-o,C:\Projects\Greece2023\Aphrodite statue on Milos_upscayl_4x_ultrasharp.jpg,-s,4,-m,C:\Program Files\Upscayl\resources\models,-n,ultrasharp,-g,0,-f,png
🐞 BACKEND REPORTED:  👶 Updating Child Processes:  [object Object]
🐞 BACKEND REPORTED:  🛑 Updating Stopped:  false
🐞 BACKEND REPORTED:  image upscayl:  [0 NVIDIA GeForce RTX 2080 Ti]  queueC=2[8]  queueG=0[16]  queueT=1[2]
[0 NVIDIA GeForce RTX 2080 Ti]  bugsbn1=0  bugbilz=22  bugcopc=0  bugihfa=0
[0 NVIDIA GeForce RTX 2080 Ti]  fp16-p/s/a=1/1/1  int8-p/s/a=1/1/1
[0 NVIDIA GeForce RTX 2080 Ti]  subgroup=32  basic=1  vote=1  ballot=1  shuffle=1

🚧 UPSCAYL_PROGRESS:  [0 NVIDIA GeForce RTX 2080 Ti]  queueC=2[8]  queueG=0[16]  queueT=1[2]
[0 NVIDIA GeForce RTX 2080 Ti]  bugsbn1=0  bugbilz=22  bugcopc=0  bugihfa=0
[0 NVIDIA GeForce RTX 2080 Ti]  fp16-p/s/a=1/1/1  int8-p/s/a=1/1/1
[0 NVIDIA GeForce RTX 2080 Ti]  subgroup=32  basic=1  vote=1  ballot=1  shuffle=1

🐞 BACKEND REPORTED:  image upscayl:  0.00%

🚧 UPSCAYL_PROGRESS:  0.00%

🐞 BACKEND REPORTED:  image upscayl:  0.07%

🚧 UPSCAYL_PROGRESS:  0.07%

🐞 BACKEND REPORTED:  image upscayl:  0.15%

🚧 UPSCAYL_PROGRESS:  0.15%

🐞 BACKEND REPORTED:  image upscayl:  0.22%

🚧 UPSCAYL_PROGRESS:  0.22%

🐞 BACKEND REPORTED:  image upscayl:  0.30%

🚧 UPSCAYL_PROGRESS:  0.30%

🐞 BACKEND REPORTED:  image upscayl:  0.37%

🚧 UPSCAYL_PROGRESS:  0.37%

🐞 BACKEND REPORTED:  image upscayl:  0.45%

🚧 UPSCAYL_PROGRESS:  0.45%

🐞 BACKEND REPORTED:  image upscayl:  0.52%

🚧 UPSCAYL_PROGRESS:  0.52%

🐞 BACKEND REPORTED:  image upscayl:  0.60%


Text removed here to reduce the size of the message to the imposed limit of 65K.


🚧 UPSCAYL_PROGRESS:  90.40%

🐞 BACKEND REPORTED:  image upscayl:  90.48%

🚧 UPSCAYL_PROGRESS:  90.48%

🐞 BACKEND REPORTED:  image upscayl:  90.55%

🚧 UPSCAYL_PROGRESS:  90.55%

🐞 BACKEND REPORTED:  💯 Done upscaling
🐞 BACKEND REPORTED:  ♻ Scaling and converting now...
🐞 BACKEND REPORTED:  📐 Processing Image:  [object Object]
🐞 BACKEND REPORTED:  ❌ Error processing (scaling and converting) the image. Please report this error on GitHub. Error: Input file is missing: C:\Projects\Greece2023\Aphrodite statue on Milos_upscayl_4x_ultrasharp.jpg
🔄 Resetting image paths
🔄 Resetting image paths
🔄 Resetting image paths
🐞 BACKEND REPORTED:  🖼️ Updating Image Path:  C:\Projects\Greece2023\White tower.jpg
🐞 BACKEND REPORTED:  📄 Selected File Path:  C:\Projects\Greece2023\White tower.jpg
🖼 Selected Image Path:  C:\Projects\Greece2023\White tower.jpg
📁 Selected Image Directory:  C:\Projects\Greece2023
🖼 imagePath:  C:\Projects\Greece2023\White tower.jpg
🔤 Extension:  jpg
🔄 Resetting Upscaled Image Path
🏁 UPSCAYL
🐞 BACKEND REPORTED:  📝 Updating Overwrite:  false
🐞 BACKEND REPORTED:  ✅ Upscayl Variables:  [object Object]
🐞 BACKEND REPORTED:  📢 Upscayl Command:  -i,C:\Projects\Greece2023\White tower.jpg,-o,C:\Projects\Greece2023\White tower_upscayl_4x_ultrasharp.jpg,-s,4,-m,C:\Program Files\Upscayl\resources\models,-n,ultrasharp,-g,0,-f,png
🐞 BACKEND REPORTED:  👶 Updating Child Processes:  [object Object],[object Object]
🐞 BACKEND REPORTED:  🛑 Updating Stopped:  false
🐞 BACKEND REPORTED:  image upscayl:  [0 NVIDIA GeForce RTX 2080 Ti]  queueC=2[8]  queueG=0[16]  queueT=1[2]
[0 NVIDIA GeForce RTX 2080 Ti]  bugsbn1=0  bugbilz=0  bugcopc=0  bugihfa=0
[0 NVIDIA GeForce RTX 2080 Ti]  fp16-p/s/a=1/1/1  int8-p/s/a=1/1/1
[0 NVIDIA GeForce RTX 2080 Ti]  subgroup=32  basic=1  vote=1  ballot=1  shuffle=1

🚧 UPSCAYL_PROGRESS:  [0 NVIDIA GeForce RTX 2080 Ti]  queueC=2[8]  queueG=0[16]  queueT=1[2]
[0 NVIDIA GeForce RTX 2080 Ti]  bugsbn1=0  bugbilz=0  bugcopc=0  bugihfa=0
[0 NVIDIA GeForce RTX 2080 Ti]  fp16-p/s/a=1/1/1  int8-p/s/a=1/1/1
[0 NVIDIA GeForce RTX 2080 Ti]  subgroup=32  basic=1  vote=1  ballot=1  shuffle=1

🐞 BACKEND REPORTED:  image upscayl:  0.00%

🚧 UPSCAYL_PROGRESS:  0.00%
Text removed here to reduce the size of the file to 65K


🐞 BACKEND REPORTED:  image upscayl:  76.19%

🚧 UPSCAYL_PROGRESS:  76.19%

🐞 BACKEND REPORTED:  image upscayl:  76.25%

🚧 UPSCAYL_PROGRESS:  76.25%

🐞 BACKEND REPORTED:  💯 Done upscaling
🐞 BACKEND REPORTED:  ♻ Scaling and converting now...
🐞 BACKEND REPORTED:  📐 Processing Image:  [object Object]
🐞 BACKEND REPORTED:  ❌ Error processing (scaling and converting) the image. Please report this error on GitHub. Error: Input file is missing: C:\Projects\Greece2023\White tower_upscayl_4x_ultrasharp.jpg
🔄 Resetting image paths
🔄 Resetting image paths
⚙️ Getting saveImageAs from localStorage:  jpg
⚙️ Getting model from localStorage:  {"label":"General Photo (Ultrasharp)","value":"ultrasharp"}
⚙️ Getting gpuId from localStorage:  0
⚙️ Getting rememberOutputFolder from localStorage:  false
⚙️ Setting compression to 100%

Describe the Bug

When attempting to run Upscayl on the image "C:\Projects\Greece2023\Aphrodite statue on Milos.jpg" an error occurs and no upscaled image is produced. Upscayl displays a popup message that indicates that there is an error:

Error processing (scaling and converting) the image. Please report this error on Upscayl GitHub issues page.

The percentage completion counter is just above 90% when the dialog is displayed.

I am using Upscayl 2.8.6.

Attempts to upscale the same image in earlier versions lead to the filing of issue #439. That issue was closed as a memory allocation problem. The image in question is a 51M byte image. The image is too large to upload to github, but could be transferred in other ways if need be.

My GPU seems to operate at about the 58% level, It has 11Gb of memory of which only about 4.3 Gb is used. My machine has 64Gb of memory an memory usage is about 59%

To Reproduce

From the GUI, select the image to be upscaled followed by clicking on the purple UPSCAYL button.

Version/Commit Hash

2.8.6

OS Specifics

Windows 10, Version2H2 (OS Build 19045.3324)

Expected Behavior

The image should have upscaled and a new upscaled image written to the source directory.

Screenshots

No response

NayamAmarshe · 2023-09-26T01:29:26Z

You can disable post processing for large images in the settings tab.

As for the image not being processed, I'd have to test it myself to debug it.

SpiritPowerTX · 2023-09-26T01:35:20Z

you can cut the big image with smaller tiles, upcale tiles and rebuild the final picture

aaronliu0130 · 2023-09-26T11:35:51Z

It probably wouldn’t be continuous

SpiritPowerTX · 2023-09-26T23:19:33Z

It probably wouldn’t be continuous

Yes I know !
The solution is : you must cut into tiles two times :

one time for upscale all "A tiles" in the picture
and a second time at offset 50% X and 50% Y of each "B tiles" and redo the upcale of all these new "B tiles" !
final step is => blend tiles A with tiles B of 0% to 100% transparency at the precise separations between all the "A tiles" for cover the "no-continuous" effect.

You can modify this as you want and optimize it, but this is one of my ideas 😉
Note that will be around x2 cost of GPU time, but it would be awesome for very large pictures that "regular upscayling" doesn't work properly.

aaronliu0130 · 2023-09-27T00:50:36Z

I'm not sure what you mean, what are A and B tiles?

Also, regular upscayling still works properly, it's just that post-processing (adding original image metadata) doesn't work.

stevehorwitz · 2023-09-27T01:19:10Z

Are you sure that this problem is caused by a large image or low memory? During the running of Upscayl on this image, my machine doesn't appear to exceed 60% capacity. What's for sure is that a 51 Mb image shouldn't be considered large anymore. The latest iPhone, iPhone 15, images are about this size.

aaronliu0130 · 2023-09-27T01:26:45Z

The issue you linked about memory is different. That one has 20:29:14.927 > Γ¥î Error reading original image metadata Error: maxMemoryUsageInMB limit exceeded by at least 20MB. This one doesn't. I'm pretty sure Nayam wants you to send the picture you're trying to Upscayl.

SpiritPowerTX · 2023-09-27T03:03:24Z

I'm not sure what you mean, what are A and B tiles?

Also, regular upscayling still works properly, it's just that post-processing (adding original image metadata) doesn't work.

here is picture for explain it :

stevehorwitz · 2023-09-27T03:04:29Z

The image is available on Google Drive:

https://drive.google.com/file/d/1e-9U1cY3y7xNWbI7nybl1GQTjt-o_URF/view?usp=sharing

SpiritPowerTX · 2023-09-27T03:26:42Z

I'm not sure what you mean, what are A and B tiles?
Also, regular upscayling still works properly, it's just that post-processing (adding original image metadata) doesn't work.

and now here is the mask (transparency : black = 0% / white = 100%) to apply on upscaled B-tiles for blend on-top of upscaled A-tiles, for remove the "no-continuous" effect :

tuxgirl · 2023-11-05T19:32:05Z

I am also having this problem. I run into it either by manually running upscayl on a file that I've already run upscayl on, and also when trying to do a double upscayl at one time.

github-actions · 2023-12-06T00:15:18Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this is still happening, please reply to indicate so.

stevehorwitz · 2023-12-07T18:42:57Z

This problem reproduces with version 2.9.5.

aaronliu0130 · 2023-12-07T20:31:29Z

Ok. And it can still be reproduced with post-processing disabled?

stevehorwitz · 2023-12-08T15:04:01Z

When processing with post-processing disabled, no error occurs. Unfortunately, no output is generated.

The split-screen previewer is displayed with the original input photo on the left side of the viewer. There is no image on the right side. The XXX_upscayl_4x_ultrasharp.png image is not generated in the directory.

There is no error in the LOGS.

aaronliu0130 · 2023-12-08T15:47:22Z

That’s very weird. We’ll try to reproduce it

aaronliu0130 · 2023-12-09T01:16:15Z

Reproduction successful. Mine stopped at 90.55% instead of 76.25% though.

@NayamAmarshe Any ideas?

NayamAmarshe · 2023-12-09T03:53:02Z

Reproduction successful. Mine stopped at 90.55% instead of 76.25% though.

@NayamAmarshe Any ideas?

Could it be an issue with the ncnn binary? @TGS963

TGS963 · 2023-12-09T03:56:54Z

Reproduction successful. Mine stopped at 90.55% instead of 76.25% though.

@NayamAmarshe Any ideas?

Could it be an issue with the ncnn binary? @TGS963

I'll need to test it out to know for sure

github-actions · 2024-01-09T00:16:03Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this is still happening, please reply to indicate so.

stevehorwitz · 2024-02-02T17:15:03Z

The nature of this problem has changed. With the latest update, image processing completes. There is no output file, however.

NayamAmarshe · 2024-02-03T18:26:57Z

Yeah we're looking into it. It seems to be an issue that needs to be fixed in ncnn repository.

stevehorwitz · 2024-02-19T17:18:55Z

This problem still reproduces with 2.9.9. Processing completes, but no output is produced.

NayamAmarshe · 2024-02-19T17:24:27Z

I suppose we'll have to put a limit on the images that you can Upscayl.

61 Mb is quite a large picture already. I'm not sure if Upscayl's processing adds too much to it when you can just scale using the regular algorithms.

I guess the only real way is to put it in JPG or WebP, reduce the size, and then process it.

stevehorwitz · 2024-02-20T22:01:19Z

Is there a technical reason why larger pictures cannot be scaled larger? For example, upscaly doesn't appear to be running out of resources such as memory or disk. It doesn't appear to be timing out.

What is the underlying source of the failure? Is there a function that is failing based on the large size? If so, what is the cause, and how can it be fixed? Could the upscale operation be successful but the output write operation be failing? Without knowing the technical reason that upscaling is failing, it is difficult to come to the conclusion that 50 M images cannot be scaled.

50 M pictures are no longer particularly large. The Apple iPhone produces pictures that are that large. The new Hasselblad 100C camera produces 100 M pictures that are twice that size.

I will note that processing has become considerably slower following the update to 2.9.9.

tarker12 · 2024-02-24T19:55:52Z

I am having same issue, small images are fine but upscaling a 8000x6000 pixel photo doesnt work. GPU acceleration enabled, high preformance setting for upscayl and it still fails.
I am using a 3070 nividia card, how can this not work?

Logs: 🐞 BACKEND REPORTED:  💾 Updating Save Output Folder:  false
⚙️ Getting saveImageAs from localStorage:  jpg
⚙️ Getting model from localStorage:  {"label":"Digital Art","value":"realesrgan-x4plus-anime"}
⚙️ Setting gpuId to empty string
🔀 Setting model to 
🔀 Setting model to realesrgan-x4plus-anime
🔄 Resetting image paths
⤵️ Dropped file:  {"type":"image/png","filePath":"C:\\Users\\Jeremy2024\\Desktop\\mat 1\\default-cloudy-dark-purple-alcohol-water-color-ink-wallpaper-1-zvt6m0ut_XU8MM54E.png","extension":"png"}
🖼 Setting image path:  C:\Users\Jeremy2024\Desktop\mat 1\default-cloudy-dark-purple-alcohol-water-color-ink-wallpaper-1-zvt6m0ut_XU8MM54E.png
🗂 Setting output path:  C:\Users\Jeremy2024\Desktop\mat 1
🖼 imagePath:  C:\Users\Jeremy2024\Desktop\mat 1\default-cloudy-dark-purple-alcohol-water-color-ink-wallpaper-1-zvt6m0ut_XU8MM54E.png
🔤 Extension:  png
⚙️ Getting saveImageAs from localStorage:  jpg
⚙️ Getting model from localStorage:  {"label":"Digital Art","value":"realesrgan-x4plus-anime"}
⚙️ Setting gpuId to empty string
⚙️ Getting rememberOutputFolder from localStorage:  false
⚙️ Getting saveImageAs from localStorage:  jpg
⚙️ Getting model from localStorage:  {"label":"Digital Art","value":"realesrgan-x4plus-anime"}
⚙️ Setting gpuId to empty string
🔀 Setting model to 
🔀 Setting model to realesrgan-x4plus-anime
🔄 Resetting Upscaled Image Path
🏁 UPSCAYL
🐞 BACKEND REPORTED:  🖼️ Updating No Image Processing:  false
🐞 BACKEND REPORTED:  📐 Updating Compression:  0
🐞 BACKEND REPORTED:  Is Default Model? :  true
🐞 BACKEND REPORTED:  ✅ Upscayl Variables:  {"model":"realesrgan-x4plus-anime","gpuId":null,"saveImageAs":"jpg","inputDir":"C:\\Users\\Jeremy2024\\Desktop\\mat 1","outputDir":"C:\\Users\\Jeremy2024\\Desktop\\mat 1","fullfileName":"default-cloudy-dark-purple-alcohol-water-color-ink-wallpaper-1-zvt6m0ut_XU8MM54E.png","fileName":"default-cloudy-dark-purple-alcohol-water-color-ink-wallpaper-1-zvt6m0ut_XU8MM54E","initialScale":"4","desiredScale":"2","outFile":"C:\\Users\\Jeremy2024\\Desktop\\mat 1\\default-cloudy-dark-purple-alcohol-water-color-ink-wallpaper-1-zvt6m0ut_XU8MM54E_upscayl_2x_realesrgan-x4plus-anime.jpg","compression":0}
🐞 BACKEND REPORTED:  📢 Upscayl Command:  -i,C:\Users\Jeremy2024\Desktop\mat 1\default-cloudy-dark-purple-alcohol-water-color-ink-wallpaper-1-zvt6m0ut_XU8MM54E.png,-o,C:\Users\Jeremy2024\Desktop\mat 1\default-cloudy-dark-purple-alcohol-water-color-ink-wallpaper-1-zvt6m0ut_XU8MM54E_upscayl_2x_realesrgan-x4plus-anime.jpg,-s,4,-m,D:\SecondaryProgramFolder\Upscayl\resources\models,-n,realesrgan-x4plus-anime,-f,jpg
🐞 BACKEND REPORTED:  👶 Updating Child Processes:  {"binary":"D:\\SecondaryProgramFolder\\Upscayl\\resources\\bin\\upscayl-bin","args":["D:\\SecondaryProgramFolder\\Upscayl\\resources\\bin\\upscayl-bin","-i","C:\\Users\\Jeremy2024\\Desktop\\mat 1\\default-cloudy-dark-purple-alcohol-water-color-ink-wallpaper-1-zvt6m0ut_XU8MM54E.png","-o","C:\\Users\\Jeremy2024\\Desktop\\mat 1\\default-cloudy-dark-purple-alcohol-water-color-ink-wallpaper-1-zvt6m0ut_XU8MM54E_upscayl_2x_realesrgan-x4plus-anime.jpg","-s","4","-m","D:\\SecondaryProgramFolder\\Upscayl\\resources\\models","-n","realesrgan-x4plus-anime","-f","jpg"]}
🐞 BACKEND REPORTED:  🛑 Updating Stopped:  false
🐞 BACKEND REPORTED:  image upscayl:  [0 NVIDIA GeForce RTX 3070]  queueC=2[8]  queueG=0[16]  queueT=1[2]
[0 NVIDIA GeForce RTX 3070]  bugsbn1=0  bugbilz=0  bugcopc=0  bugihfa=0
[0 NVIDIA GeForce RTX 3070]  fp16-p/s/a=1/1/1  int8-p/s/a=1/1/1
[0 NVIDIA GeForce RTX 3070]  subgroup=32  basic=1  vote=1  ballot=1  shuffle=1

🚧 UPSCAYL_PROGRESS:  [0 NVIDIA GeForce RTX 3070]  queueC=2[8]  queueG=0[16]  queueT=1[2]
[0 NVIDIA GeForce RTX 3070]  bugsbn1=0  bugbilz=0  bugcopc=0  bugihfa=0
[0 NVIDIA GeForce RTX 3070]  fp16-p/s/a=1/1/1  int8-p/s/a=1/1/1
[0 NVIDIA GeForce RTX 3070]  subgroup=32  basic=1  vote=1  ballot=1  shuffle=1

stevehorwitz · 2024-03-16T19:46:28Z

This problem reproduces with version 2.10.0. Processing begins normally, but at about 90% complete, processing stops. There is no error message, and no output has been created.

gerardbosch · 2024-04-17T10:55:42Z

I'm facing this issue with relatively small input images (10-15MB JPG): Upscale takes a long time and when finally reaches 100%, no output file is produced.

It works fine for smaller inputs like 3-7MB JPG, and 3-7MB PNG.

Tested on a MacBook Air M1 (2020), macOS Sonoma 14.4.1.

NayamAmarshe · 2024-04-18T04:41:20Z

The official limit is around 6500x6500. Anything above that could potentially cause the binary to crash.

stevehorwitz · 2024-04-18T14:54:42Z

If the original reproduction image is cropped to 6500x6500, Upscayl succeeds.

There is no split screen display, however.

The crop loses about 20% of the image when cropped.

Is the 6500x6500 limit built in, and can the limit be increased allowing larger images to be processed?

NayamAmarshe · 2024-04-18T22:28:48Z

If the original reproduction image is cropped to 6500x6500, Upscayl succeeds.

There is no split screen display, however.

The crop loses about 20% of the image when cropped.

Is the 6500x6500 limit built in, and can the limit be increased allowing larger images to be processed?

It varies according to the hardware sometimes but I found that 6500x6500 is the usual limit. You could try downsizing to 6500 pixels in width.

stevehorwitz · 2024-05-02T13:31:58Z

This problem reproduces with version 2.11.0.

stevehorwitz added the bug Something isn't working label Sep 25, 2023

github-actions bot added the stale We lack your response. Please reply to re-start the issue label Dec 6, 2023

github-actions bot removed the stale We lack your response. Please reply to re-start the issue label Dec 8, 2023

aaronliu0130 added this to the 2.9.x milestone Dec 9, 2023

aaronliu0130 mentioned this issue Dec 11, 2023

Error: Input file is missing #590

Closed

4 tasks

github-actions bot added the stale We lack your response. Please reply to re-start the issue label Jan 9, 2024

aaronliu0130 added HIGH PRIORITY AAAAAAAAAAAAAAAAAAA!! and removed stale We lack your response. Please reply to re-start the issue labels Jan 9, 2024

NayamAmarshe assigned TGS963 Jan 31, 2024

aaronliu0130 added the help-wanted Extra attention is needed label Feb 24, 2024

gerardbosch mentioned this issue Apr 17, 2024

Is there a size limit? #768

Closed

3 tasks

aaronliu0130 removed this from the 2.9.5 milestone May 2, 2024

NayamAmarshe changed the title ~~Upscayl fails when upscaling large image~~ [BUG][BIG IMAGE] Upscayl fails when upscaling large image May 14, 2024

NayamAmarshe changed the title ~~[BUG][BIG IMAGE] Upscayl fails when upscaling large image~~ [BUG][MEMORY LIMIT] Upscayl fails when upscaling large image May 14, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[BUG][MEMORY LIMIT] Upscayl fails when upscaling large image #493

[BUG][MEMORY LIMIT] Upscayl fails when upscaling large image #493

stevehorwitz commented Sep 25, 2023

NayamAmarshe commented Sep 26, 2023

SpiritPowerTX commented Sep 26, 2023

aaronliu0130 commented Sep 26, 2023

SpiritPowerTX commented Sep 26, 2023 •

edited

aaronliu0130 commented Sep 27, 2023 •

edited

stevehorwitz commented Sep 27, 2023

aaronliu0130 commented Sep 27, 2023

SpiritPowerTX commented Sep 27, 2023

stevehorwitz commented Sep 27, 2023

SpiritPowerTX commented Sep 27, 2023 •

edited

tuxgirl commented Nov 5, 2023

github-actions bot commented Dec 6, 2023

stevehorwitz commented Dec 7, 2023

aaronliu0130 commented Dec 7, 2023

stevehorwitz commented Dec 8, 2023

aaronliu0130 commented Dec 8, 2023

aaronliu0130 commented Dec 9, 2023

NayamAmarshe commented Dec 9, 2023

TGS963 commented Dec 9, 2023

github-actions bot commented Jan 9, 2024

stevehorwitz commented Feb 2, 2024

NayamAmarshe commented Feb 3, 2024

stevehorwitz commented Feb 19, 2024

NayamAmarshe commented Feb 19, 2024

stevehorwitz commented Feb 20, 2024

tarker12 commented Feb 24, 2024 •

edited by aaronliu0130

stevehorwitz commented Mar 16, 2024

gerardbosch commented Apr 17, 2024 •

edited

NayamAmarshe commented Apr 18, 2024

stevehorwitz commented Apr 18, 2024

NayamAmarshe commented Apr 18, 2024

stevehorwitz commented May 2, 2024

[BUG][MEMORY LIMIT] Upscayl fails when upscaling large image #493

[BUG][MEMORY LIMIT] Upscayl fails when upscaling large image #493

Comments

stevehorwitz commented Sep 25, 2023

Checklist

Paste the logs

Describe the Bug

To Reproduce

Version/Commit Hash

OS Specifics

Expected Behavior

Screenshots

NayamAmarshe commented Sep 26, 2023

SpiritPowerTX commented Sep 26, 2023

aaronliu0130 commented Sep 26, 2023

SpiritPowerTX commented Sep 26, 2023 • edited

aaronliu0130 commented Sep 27, 2023 • edited

stevehorwitz commented Sep 27, 2023

aaronliu0130 commented Sep 27, 2023

SpiritPowerTX commented Sep 27, 2023

stevehorwitz commented Sep 27, 2023

SpiritPowerTX commented Sep 27, 2023 • edited

tuxgirl commented Nov 5, 2023

github-actions bot commented Dec 6, 2023

stevehorwitz commented Dec 7, 2023

aaronliu0130 commented Dec 7, 2023

stevehorwitz commented Dec 8, 2023

aaronliu0130 commented Dec 8, 2023

aaronliu0130 commented Dec 9, 2023

NayamAmarshe commented Dec 9, 2023

TGS963 commented Dec 9, 2023

github-actions bot commented Jan 9, 2024

stevehorwitz commented Feb 2, 2024

NayamAmarshe commented Feb 3, 2024

stevehorwitz commented Feb 19, 2024

NayamAmarshe commented Feb 19, 2024

stevehorwitz commented Feb 20, 2024

tarker12 commented Feb 24, 2024 • edited by aaronliu0130

stevehorwitz commented Mar 16, 2024

gerardbosch commented Apr 17, 2024 • edited

NayamAmarshe commented Apr 18, 2024

stevehorwitz commented Apr 18, 2024

NayamAmarshe commented Apr 18, 2024

stevehorwitz commented May 2, 2024

SpiritPowerTX commented Sep 26, 2023 •

edited

aaronliu0130 commented Sep 27, 2023 •

edited

SpiritPowerTX commented Sep 27, 2023 •

edited

tarker12 commented Feb 24, 2024 •

edited by aaronliu0130

gerardbosch commented Apr 17, 2024 •

edited