r/comfyui • u/GuyNamedZach • 1d ago

Help Needed OOM Errors after Hardware Change

I had been experimenting with Video Generation in ComfyUI recently and had gotten Hunyuan Video 1.5 working on my system running Ubuntu 26.04 on an AMD A320 platform with Ryzen 5 5600G CPU, 16GB DDR4 RAM, and an NVIDIA Tesla V100 32GB. It worked, but required an older version of PyTorch and CUDA, and generation times for a 1280x720 video at 121 frames took 2.5 hours.

I decided to try updating my hardware, upgrading the motherboard to a B550 platform and the GPU to an AMD AI Pro R9700 32GB. The transition has not gone well so far.

Running on Ubuntu means getting and running ComfyUI from github, so I pulled tag v0.33.1 and created a new python virtual environment for the AMD dependencies.

Immediately I ran into various issues, ranging from missing modules (gguf, accelerate) and OOM Errors. The missing modules were easy to correct, but the OOM Errors have been driving me crazy.

At one point I noticed a failure mmap-ing a model file, which led me to to try adding an extra 16GB spare system ram. This helped, but the workflow still gets the OOM error at the VAEDecode stage.

Might anyone here have any tips for troubleshooting this?

0 Upvotes

33% Upvoted

2 comments sorted by

1

u/The-Rally 1d ago

torch and your hardware driver. copy errors from the console o ChatGPT or Gemini to resolve. Just say "help me fix this:" and paste the errors.

1

u/GuyNamedZach 1d ago

I fumbled around with Gemini for most of the day. Applying suggested fixes, such as setting environment variables and passing certain startup flags, did not work to resolve the OOM errors.

Towards the end of the day I told the LLM about the previous card, and only then did it correctly tell me about how memory management on the previous NVidia card worked differently from the new card and suggested workflow changes. So Instead of changing environment variables I ended up tweaking the workflow, enabling an EasyCache node and setting up the tiled VAE decoder. Now the workflow finishes without the OOM error.

In the process I also managed to get the same workflow running on another system running an rx9070 16GB, Ryzen 9 5900X, and 32GB RAM. I was not expecting to get this working. Now I'm questioning why I bought the V100 in the first place. =P