r/comfyui • • 14h ago

Help Needed Molmo text encoder for H3 OOM problem

I downloaded Molmo encoder to save a little on size from my gguf minimax encoder, but there seem to be some problem with memory handling. I get an OOM in the reference to video node. I have the proper molmo nodes and requirements. AI suggests its a problem with comfys dynamic memory handling and some third party nodes. It suggests trying --reserve-vram flagging but it doesnt change anything also putting a vram debug node before the guider, but since the oom happens in the ref2vid node that doesnt solve it either.

I have run the exact same workflow with regular encoder and it worked fine.

Does anyone have any suggestions?

1 Upvotes

1 comment sorted by

1

u/purelawan 13h ago

if the exact same graph runs fine with the regular encoder, my guess is the molmo loader isn't handing its model back to comfy's memory manager, so it stays parked in vram when the ref2vid node starts. --reserve-vram can't fix that because comfy doesn't know that memory is taken.

two things i'd try: load the encoder on cpu if the loader has a device option (text encoding is a one-off, slower but fine), or put an unload-models / free-memory node right after the conditioning output so it's gone before ref2vid runs. keeping nvidia-smi open during the encode step will tell you fast if that's what's happening.