-
Notifications
You must be signed in to change notification settings - Fork 26.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Out of memory while using Upscaler #16181
Comments
from what you have written here I don't even know what version of webui you are using |
"Platform": "Windows-10-10.0.22631-SP0", |
It seems to me that the Hires.fix isn't just an Upscaler. I mean that this bug could be explained only by assuming that other complex calculations besides image upscaling take place when Hires.fix is running. Even if this is the case, you need to change the description of this operation on the Hires.fix tab. Because, right now from the description, it seems that this tab just starts the Upscaler after the image is generated.
|
Massive PEBKAC. |
The only problem here is that you downloaded a software that has been out for a long time and decided to report something as a software issue when you obviously haven't read a single letter from the documentation, alerting the devs to a potential issue. https://github.com/AUTOMATIC1111/stable-diffusion-webui/wiki/Features#hires-fix Don't bloat the software's Issues page with your personal problems of reading comprehension, this is used to track legitimate problems. |
Checklist
What happened?
Upscaling the image with R-ESRGAN 4x+ (512x512 to 2048x2048) in Hires.fix tab consumes more than 32 GB of memory.
Just don't give me the nonsense that this operation needs that much memory.
Looks like there's some kind of memory leak in the webui.
So much memory is not consumed when upscaling an image in Extras tab.
Steps to reproduce the problem
What should have happened?
What browsers do you use to access the UI ?
Microsoft Edge
Sysinfo
Console logs
Additional information
No response
The text was updated successfully, but these errors were encountered: