-
Notifications
You must be signed in to change notification settings - Fork 27.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
[Bug]: Cannot locate TCMalloc #10117
Comments
Did you install TCMalloc from your OS repositories? Here is mine on Ubuntu
|
On my system the reason for this was that |
On Ubuntu-22.04 with WSL2, installing google-perftools improved the situation |
this is helpful in ubuntu20.04: |
Hi, can you tell me how to solve this, thank you. |
I added the line
to |
thanks, this is worked for me ! |
Thank you very much. This solved the problem in Debian. |
If you are in the Centos system, try performing the following actions
|
This is not an error, it's just a warning that tcmalloc isn't being used. Anyway, closing because there's a bunch of solutions in this thread, mainly "installing tcmalloc". 😁 |
On Archlinux:
|
Great. This works for me. |
I had to install these packages on open suse |
hey, thank you |
Just curious, do I need to re-install stable-diffusion-webui after I installed TCMalloc, because it already built with GCC without it? Or can I just install TCMalloc after installing stable-diffusion-webui ? |
You do not need to reinstall stable-diffusion-webui, it is not a compiled binary. The tcmalloc reference is initialized in webui.sh and was introduced in commit 8af4b3b |
In openSUSE 15.5 change line in webui.sh |
For Debian: |
Is there an existing issue for this?
What happened?
when i run webui.sh on centos server, it came out a error : Cannot locate TCMalloc (improves CPU memory usage)
Steps to reproduce the problem
What should have happened?
this error should not happen
Commit where the problem happens
5ab7f21
What platforms do you use to access the UI ?
No response
What browsers do you use to access the UI ?
No response
Command Line Arguments
List of extensions
Console logs
Additional information
No response
The text was updated successfully, but these errors were encountered: