Skip to content
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

Extras tab keep upscaling the old image when using copy/paste, also, right clic copy the resulting image doesn't work #503

Closed
Mozoloa opened this issue Sep 15, 2022 · 3 comments
Labels
bug Report of a confirmed bug

Comments

@Mozoloa
Copy link
Collaborator

Mozoloa commented Sep 15, 2022

Describe the bug
In the extras tab, if you paste an image to upscale it, then paste another one (seems to be especially if the size is the same), it's gonna keep upscaling the first one

Also copying the upscaled image doesn't work anymore, nothing goes into the clipboard

To Reproduce
Paste an image to upscale it in the extras tap, upscale it, then remove the previous one & paste another one (seems to be especially if the size is the same), it's gonna re upscale the first one. In the same time try to copy the upscaled image it doesn't work either.

Expected behavior
Should upscale the new one and right click copy should work

Desktop (please complete the following information):

  • OS: Windows
  • Browser : Brave
  • Commit revision : cde49dc
@Mozoloa Mozoloa added the bug Report of a confirmed bug label Sep 15, 2022
@NYKevin
Copy link

NYKevin commented Oct 4, 2022

I can reproduce substantially the same bug with this procedure:

  1. Make anything with txt2img and send it to inpainting.
  2. Inpaint it with batch size > 1.
  3. Pick any of the inpainting outputs and send it to extras.
  4. Upscale.
  5. Pick a different inpainting output and send it to extras.
  6. Try to upscale that. It'll output the same image as you got in step 4, and if you use LDSR, it'll do so much faster than is normally possible (implying it's pulling from some kind of cache that needs to be invalidated).

@ClashSAN
Copy link
Collaborator

@Mozoloa can this issue be closed now?

@Mozoloa
Copy link
Collaborator Author

Mozoloa commented Oct 31, 2022

Yep that seems fixed

@Mozoloa Mozoloa closed this as completed Oct 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Report of a confirmed bug
Projects
None yet
Development

No branches or pull requests

3 participants