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

VRAM management could improve #104

Open
andreszs opened this issue Jan 14, 2025 · 0 comments
Open

VRAM management could improve #104

andreszs opened this issue Jan 14, 2025 · 0 comments
Assignees

Comments

@andreszs
Copy link

andreszs commented Jan 14, 2025

Please take no offense, but the demo workflow is probably one of the most unstable I've ever tried and all problems seem to be memory-related.

Summary of errors

  1. SamplerCustomAdvanced: Allocation on device <- requires lowering settings, then it will appear again and can only be avoided by constantly restarting comfyui after each successful prompt. Unloading models does not help.
  2. Expected all tensors to be on the same device, but found at least two devices, cpu and cuda:0! (when checking argument for argument mat2 in method wrapper_CUDA_bmm) -> this one appears in subsequent prompts
  3. mat1 and mat2 must have the same dtype, but got Float and BFloat16 -> introduced by disabling mixed_precision to avoid the previous error

It's simply impossible to benchmark this workflow since it runs only once per comfyui session.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants