-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Dream.py process unexpectedly killed while initializing #342
Comments
Is it possible that you are running out of main memory (RAM, not VRAM)? During model loading, the underlying AI library will transiently use up to 9G of RAM before settling down into the 4-5G range. If you do have sufficient RAM, then try running "ulimit -a" and looking at the "max memory size" setting to see if perhaps it is set to a limited amount. |
The VmmemWSL-process seems to use about 6-7 GB of ram before the process is shut down. According to Task Manager in Windows i reach about 85% memory usage, not sure if that is accurate, but if it is it doesnt seem like i run out of memory. ulimit -a outputs the following information;
|
Could be Windows doesn't like WSL using that much RAM that quickly... 🤔 I'm not familiar with how Windows manages WSL RAM usage - it's possible that it's like a "standard" virtual machine, i.e. it has a hard limit on RAM when the environment is created. |
I have the same issue. Did you solve it? |
I have the usual problem if I try to run the current version on Colab Free and it is the OS killing the process. |
I tried it but it didn't work. Ultimately, I installed it on Windows, and ran perfectly! |
@gmthedoc |
Describe your environment
Describe the bug
The text was updated successfully, but these errors were encountered: