[Feature Request]: Unload ReActor Models and VRAM Debug

[Taruvi]

I've had a problem that's bugged me for a long, long time to do with VRAM being clogged by something. I've tracked it down to ReActor. Whenever I've used it, it would keep about 2.5GB VRAM clogged up until I completely restarted Swarm/Comfy.

It got to the point where I've only been using ReActor sparingly, to the point of hardly ever really using it anymore.

In fact, I reported it in the Swarm repo way back. I think around that time I was doing lots of generating images, then doing I2V in WAN, and that's why ReActor was always taking up that annoying little bit of VRAM all the time that would give me constant OOMs until I fully restarted everything.

However...

I did a little bit of digging around and I see there's been a node there this whole time that's perfect for fixing this problem:

I've been testing this in a Comfy Workflow and it does the job exactly as the name implies.

Further to this, I have it hooked up to KJ's VRAM Debug node:

With both combined, my VRAM usage drops to next to nothing after every generation.

VRAM Debug works very well in an extension I currently use a lot: SwarmUI SeedVR2 Upscaler Extension.

The readme for that says:

VRAM Cleanup: Automatically unloads the main generation model before upscaling (requires KJNodes)

It works great.

Considering Unload ReActor Models is already included in ReActor anyway, and VRAM Debug is part of KJ's Nodes which I suppose a lot of people have installed already, my feature request is:

1. Add a toggle in the extension for the Unload ReActor Models node to run it after every generation
2. Add a toggle in the extension for the VRAM Debug node to run after every generation

Every little bit helps for those of us stuck with what we have due to stupid GPU prices.

Thanks.

[Quaggles]

I've added the ReActor Unload Models option as an advanced parameter in commit e5cf502

For the KJNodes VRAM Debug that probably makes sense so be it's own extension that adds VRAM Debug to the end of any workflow, if I added it in FaceTools people would have to install the node manually to use that function or I'd have to add another node install button that would show up constantly for people that didn't want to have KJNodes installed.

[Taruvi]

For VRAM Debug, fair enough. I don't know the technicalities of it all - I didn't know if an extension can detect already installed nodes and use their capabilities. But unloading the ReActor model was the main thing. Speaking of which...

I can't seem to find it anywhere. I have Display Advanced Options checked but it's not there. Neither is it in User -> Parameter Configuration -> Group: ReActor.

I see in the log:

2026-02-25 12:09:45.460 [Debug] Don't need to rebuild extension src/Extensions/SwarmUI-FaceTools/SwarmUI-FaceTools.csproj, already built.

I know every time there's a SwarmUI update that extensions get rebuilt. So would the extension need to be rebuilt in order to see the new option?

Also, is there a reason why your extension randomly enables itself sometimes when I start up SwarmUI? Because of the ReActor models staying loaded, I've had your extension disabled until I need it, then I manually enable it and do whatever I need to. But sometimes it just enables itself between restarts. I can't tell you what triggers it or how to reproduce it. It just happens all by itself for whatever reason that I can't explain. I should say it only happens with your extension, though I only have two extensions installed so it's not exactly a huge sample size.

[Quaggles]

That's strange, I just tested SwarmUI updating extensions and after the update I saw

20:17:23.074 [Debug] Building extension project: src/Extensions/SwarmUI-FaceTools\SwarmUI-FaceTools.csproj...
20:17:24.000 [Debug] Successful build output for extension project src/Extensions/SwarmUI-FaceTools\SwarmUI-FaceTools.csproj:
Determining projects to restore...
  Restored C:\Users\user\Git\AI\SwarmUI-Clean\src\Extensions\SwarmUI-FaceTools\SwarmUI-FaceTools.csproj (in 120 ms).
  SwarmUI-FaceTools -> C:\Users\user\Git\AI\SwarmUI-Clean\src\bin\extensions\SwarmExtensionSwarmUI-FaceTools\SwarmExtensionSwarmUI-FaceTools.dll

Build succeeded.
    0 Warning(s)
    0 Error(s)

and the parameter showed up after I refreshed the page. Maybe try uninstalling then reinstalling the extension?

As for it enabling itself the extension only adds ReActor nodes to the workflow if the ReActor parameter group is toggled on, if the group is disabled do you see any parameters starting with [ReActor] in the image metadata?

[Taruvi]

Did your SwarmUI update as you were starting it up, or was it already up to date before starting it? The only time I see extensions being rebuilt is when SwarmUI has been updated during startup. Otherwise, the log message about [Debug] Don't need to rebuild extension src/Extensions/SwarmUI-FaceTools/SwarmUI-FaceTools.csproj, already built. is generated.

I just started SwarmUI a short time ago (I use a Docker version). On this occasion, the ReActor extension was not enabled after this startup.

I'll give you the full verbose log file in case you can see something relevant: https://paste.denizenscript.com/View/139300

I don't see any ReActor mentions in the metadata while the extension is disabled. As a test just now:

I'm also reluctant to uninstall and reinstall, though I'll do that if necessary. The reason being is that in User -> Parameter Configuration, I've reordered several things and hidden or shown others to suit my needs. I'm not sure if uninstalling/reinstalling will necessitate have to redo these customisations.

So I'll not do that for the moment. Instead, I'll open an issue in the SwarmUI Github and see if there's something that can be done to trigger these rebuilds more reliably. After all, if there are no SwarmUI updates but there are extension updates, it feel like any new features can't be used until there is a SwarmUI update to trigger the rebuild first.

[Taruvi]

SwarmUI had an update, I restarted, the extension was rebuilt and now the setting is showing up:

2026-02-27 00:07:17.299 [Debug] Building extension project: src/Extensions/SwarmUI-FaceTools/SwarmUI-FaceTools.csproj...
MSBuild version 17.8.31+af11d4f25 for .NET
  Determining projects to restore...
  All projects are up-to-date for restore.
Time Elapsed 00:00:04.87
2026-02-27 00:07:30.830 [Debug] Successful build output for extension project src/Extensions/SwarmUI-FaceTools/SwarmUI-FaceTools.csproj:
MSBuild version 17.8.31+af11d4f25 for .NET
  Determining projects to restore...
  Restored /config/07-SwarmUI/SwarmUI/src/Extensions/SwarmUI-FaceTools/SwarmUI-FaceTools.csproj (in 8.72 sec).
  SwarmUI-FaceTools -> /config/07-SwarmUI/SwarmUI/src/bin/extensions/SwarmExtensionSwarmUI-FaceTools/SwarmExtensionSwarmUI-FaceTools.dll

Build succeeded.
    0 Warning(s)
    0 Error(s)

So it was what I thought, then: SwarmUI itself needs to trigger the extension rebuild for it to properly install any latest version.

Anyway, all done now. Thanks for the unload models option.