[Bug]: AnimateDiff does not function with the current version of a1111?

[o-l-l-i]

Is there an existing issue for this?

• [X] I have searched the existing issues and checked the recent builds/commits of both this extension and the webui

Have you read FAQ on README?

• [X] I have updated WebUI and this extension to the latest version

What happened?

After updating a1111 to the latest version yesterday, nothing seems to work in AnimatedDiff. Before this, I managed to get it to function with and without ControlNet, and generally just get it to render something.

But now, when I toggle it on, during generation it will print out a variety of errors, and all of them always end to CUDA errors:

CUDA kernel errors might be asynchronously reported at some other API call, so the stacktrace below might be incorrect. For debugging consider passing CUDA_LAUNCH_BLOCKING=1. Compile with TORCH_USE_CUDA_DSA to enable device-side assertions.

Everything else seems to be functioning OK with WebUI.

Steps to reproduce the problem

1. Go to txt2img
2. Create a prompt
3. Activate AnimateDiff, configure basic settings
4. Generate

What should have happened?

AnimateDiff renders correctly, and causes no errors.

Commit where the problem happens

webui: v1.8.0 b76cc78ad9 extension: master a3905000 2024-03-10 11:27:58 controlnet: main aa2aa812 2024-03-06 04:52:19

What browsers do you use to access the UI ?

Google Chrome, Brave

Command Line Arguments

--administrator --xformers --no-half-vae
And custom paths for:
--ckpt-dir
--embeddings-dir
--lora-dir
--vae-dir
--hypernetwork-dir
--lyco-dir
--controlnet-dir

Console logs

(I removed the beginning of this)

RuntimeError: CUDA error: device-side assert triggered
CUDA kernel errors might be asynchronously reported at some other API call, so the stacktrace below might be incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1.
Compile with `TORCH_USE_CUDA_DSA` to enable device-side assertions.

Additional information

I tried different models, both SD 1.5-based, and SDXL. Without and with ControlNet, and any extras. Just a fresh boot of WebUI and activating AnimateDiff with the default settings causes this error.

[o-l-l-i]

I tried to debug a bit more, to see what might cause this. I seem to very easily end up to a situation where this error starts to appear:

For example, I just tried this:

• Install a fresh copy of a1111.
  • use --administrator --xformers command line args.
• Install ControlNet (sd-webui-controlnet) via Extensions/Available.
• Install AnimateDiff (sd-webui-animatediff) via Extensions/Available.
• After restarting, AnimateDiff works fine.
• However, after I installed only adetailer, this setup broke down instantly. Same CUDA error, and a few other errors.

Then I tried to see where the settings/data are stored that prevents this from getting restored back to a working order.

What did not work:

• Deleting venv contents, and rebuilding the venv.
  • This had no effect, it seems. No obvious errors in the log when booting up a1111, but same CUDA errors.

What worked:

• Sorry I don't have a accurate list (I will log this more carefully later with some tool), but after I deleted the venv folder and following files, I got it working:
  • cache.json
  • config.json
  • params.txt
  • ui-config.json
  • tmp folder
  • extensions other than ControlNet and AnimateDiff

After a rebuild of the venv a1111 booted successfully, and AnimateDiff worked again.

But it would be good to figure out this, since this extension is one of the few that repeatedly breaks down, out of 20+ I quite often use.

[continue-revolution]

If you install adetailer but do not apply it to your generation, the generation should be fine. If you apply adetailer and animatediff at the same time, it seems that there is some unknown error.

If that's the case, I will close this issue and track this problem via #446 . Otherwise, feel free to re-open this issue.