-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Init Failed #78
Comments
Plus it uses so much CPU and RAM every time it tries todo that. |
try v0.0.49 |
Of what? |
nvm found |
docker image |
Yea, i am running off of the Source, But yea after pulling it doesnt consume that much CPU or RAM anymore. Phind still does not work tho. |
ok i try to fix it |
Forefront gives me this error btw: |
And the Memory Leak still happens. Its using up more than 1 GB. 8|GPT4FREE | (node:1962021) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGINT listeners added to [process]. Use emitter.setMaxListeners() to increase limit |
at almost 1.5GB now |
pull and retry |
Still the exact same issue |
Show me the log |
8|GPT4FREE | 3c6c50a5-d677-4319-bc16-b927c835e51a has been deleted |
It appears that your device cannot access the PHIND if you can access phind directly , delete http_proxy in |
How can i access PHIND? |
I am so confused. For what is the http proxy? |
After 40 mins it hat 100% CPU and 95% RAM |
PHIND still in initing but i dont care. Finally turned off the PHIND pool. |
if you dont use phind set phind_pool_size=0 |
Yea, did that. Its better now |
On Debian 11. Via Yarn
The text was updated successfully, but these errors were encountered: