-
Notifications
You must be signed in to change notification settings - Fork 322
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not enough space in the context's memory pool with ControlNet #178
Comments
Checkout my commit, i did some mod. to avoid this. The interesting part of this: FYI: i didn't calculated nothing |
I checked out that pr and it solves every issue I was having with the context's memory pool, amazing job. I'll be closing this issue then. |
Thanks, but as i wrote, i didn't calculated nothing, so this modifications "as-is". I tested it with my desktop app at many times (only with CUDA and with 12GB VRAM), and it's working fine, but i'm sceptic with it. So, use with cauction please. |
I still haven't looked carefully at the code so I'm not sure about how it works but maybe some check during compile time may optimize that parameter specifically for the gpu memory (even if that would be quite a bad choice for distributing the program). |
I think it depends on the loaded model file size (eg. lora model file size, controlnet model file size etc..), that's need to be fit in there. |
Whenever I try to use ControlNet with an input image bigger than 512x512 I keep getting
ggml_new_object: not enough space in the context's memory pool (needed 18122976, available 16777216)
.I'm currently using a HIPBlas build and have plenty of vram available.
Is this expected or is there a way to manually increase the context memory pool in the code?
The text was updated successfully, but these errors were encountered: