[Bug]: Idle VRAM usage with --always-offload-from-vram is way higher than vanilla auto1111 --medvram

[outNEXT]

Checklist

• [X] The issue exists after disabling all extensions
• [X] The issue exists on a clean installation of webui
• [ ] The issue is caused by an extension, but I believe it is caused by a bug in the webui
• [X] The issue exists in the current version of the webui
• [X] The issue has not been reported before recently
• [ ] The issue has been reported before but has not been fixed yet

What happened?

Vanilla webui with --medvram after generating once to offload will use 200,000KB of vram, Forge however (using --always-offload-from-vram) will use 800,000KB and sometimes even grows(? possibly another bug?) up to 1GB when idle.

Steps to reproduce the problem

1. Launch with --always-offload-from-vram
2. Generate once (Model is only offloaded after generating once for some reason. Different bug I guess, exists on both repos)
3. Check task manager or Operating system equivalent.

What should have happened?

Really it should try to minimise idle vram usage, I'm not sure what changed. Possibly some optimisation that medvram did that isn't done anymore?

What browsers do you use to access the UI ?

Google Chrome, Apple Safari, iOS

Sysinfo

sysinfo-2024-02-21-05-27.json

Console logs

Nothing out of the usual, regular old logs. My local repo is not currently checked out on forge branch to fetch one. But if you need one I can get one for you.

Additional information

No response

[jswag245]

Does the issue still occur with more recent commits? I'm sure some memory optimization improvements have been made since then, and I'm hoping they've fixed your issue.