Issue with Memory Not Being Released When module is Set to None in Stable Diffusion WebUI with ControlNet #16401
Unanswered
sanerone695
asked this question in
Q&A
Replies: 1 comment
-
first from what I can tell you're reporting an issue related to specifically ControlNet clarify what you mean by "ControlNet, setting the module to None." do you mean with a ControlNet
how much does the system RAM increase |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Description:
When using the Stable Diffusion WebUI with ControlNet, I encountered an issue where memory is not released properly when the module is set to None. In contrast, when the module is set to a non-None value, the memory is correctly released after the process is completed.
Details:
Environment: Stable Diffusion WebUI with ControlNet.
Behavior:
When module is set to None, the memory usage increases with each run and is not released after the task completes.
When module is set to a specific value (not None), the memory is released correctly after the task completes.
Impact: This issue causes the system's memory usage to increase progressively with each task, potentially leading to out-of-memory errors or reduced performance over time.
Potential Cause:
It appears that some internal resources or cached data are not being properly managed or released when module is None. This might be due to certain resource management logic not being triggered or properly handled in this specific scenario.
Steps to Reproduce:
Run a task using Stable Diffusion WebUI with ControlNet, setting the module to None.
Observe the memory usage after the task completes. Notice that the memory is not released.
Run the same task with module set to a non-None value and observe that the memory is released correctly after completion.
Beta Was this translation helpful? Give feedback.
All reactions