-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
Image prompt does not work in Gooble Colab's (free) service #654
Comments
I'm running into the same issue on colab where during generation it would get a connection timeout error. The console in other tab shows |
Free colab limited memory and image prompt feature requires more? I faced a similar problem when tried using free colab to make loras (during generation it would get a connection timeout error). Trying to sell my kidney, hopefully, I will get a used 3090 by next week. |
It seems like recent changes is what spikes up system memory usage. google colab has ~12-13gb of ram. Checking the resource before the crash shows system memory usage spikes past 12gb for me. As an interim workaround, I just ran Fooocus at an earlier point of commit. For example, I hope @lllyasviel finds a way to allow Fooocus to function even in lower system memory environments -- maybe as an option that can be past to the launcher? |
This branch uses less memory However we are still looking at methods to use it in a better way |
Most likely your RAM is exhausted, which is why your process is cancelled. Please check and upgrade it or your plan. See #1330, #1574, #1558 (comment) |
First of all, I would like to thank you on behalf of everyone for the amazing work you have done to create Fooocus. You are the best!
Unfortunately, the new image prompt part does not work in Gooble Colab's (free) service.
It says Image processing for a while and then it says a red Error on the screen.
In the resources of Google Colab, you can see that the system memory (not the GPU) reaches the maximum. This is probably the cause of the error.
The text was updated successfully, but these errors were encountered: