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

[Bug]: After pressing "Y" the canvas is cleared, only the last generation remains #272

Closed
BenderBlender opened this issue Dec 5, 2023 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@BenderBlender
Copy link

What happened?

After clicking on "Y" (or "ENTER" after generation), the canvas is completely cleared, leaving only the square with the latest generation. So it’s not possible to use the editor normally.

Steps to reproduce the problem

  1. Generate first image
  2. Press "Y" (all ok)
  3. Generate second image (in the other place of canvas)
  4. Press "Y" (all canvas cleared, except for the square with the current generation)

What should have happened?

After clicking on "Y" (or "ENTER" after generation), the canvas is completely cleared, leaving only the square with the latest generation. So it’s not possible to use the editor normally.

Commit where the problem happens

What platforms do you use to access openOutpaint?

Windows

What browsers do you use to access the UI ?

Google Chrome

Browser Extensions/Addons

AUTOMATIC1111 webUI Commandline Arguments

@echo off

set PYTHON=
set GIT=
set VENV_DIR=
set COMMANDLINE_ARGS=--theme=dark --opt-sdp-no-mem-attention --no-half-vae --opt-channelslast --api
set SAFETENSORS_FAST_GPU=1

call webui.bat

Additional information

@BenderBlender BenderBlender added the bug Something isn't working label Dec 5, 2023
@BenderBlender
Copy link
Author

Checked it in browser Microsoft Edge, everything is the same, so it's not because of the browser

@zero01101
Copy link
Owner

closing as duplicate of #268

@zero01101 zero01101 closed this as not planned Won't fix, can't repro, duplicate, stale Dec 9, 2023
@zero01101
Copy link
Owner

seems chromium upstream is really seeming to be the culprit here; if anyone still affected could confirm the findings in #268 (comment) that'd be awesome :)

@BenderBlender
Copy link
Author

After the last update everything worked! Thank you very much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants