Skip to content
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

macOS M4 max run exo error:infinite show : 0ther threads are currently calling into gRPc, skipping fork() handlers #554

Open
elven2016 opened this issue Dec 11, 2024 · 10 comments

Comments

@elven2016
Copy link

hardware:MacBook Pro M4 max 48g
OS:macOS15.1.1
after finished installed exo(pip install -e .), exec the command exo, the terminal infinite show the error
image
the tinychat webui can open,but chat response very slow
image
the exo terminal also show the error
image
I have reinstll many times, I. also try this in nvidia pc, it works fine,but macos run not successfuly,Please help,thanks

@NotReallyADeveloper
Copy link

I can confirm the same issue. I figured out how to make the messages go away (doing what the errors say to do), but I don't know if that is detrimental to overall performance.

@elven2016
Copy link
Author

I can confirm the same issue. I figured out how to make the messages go away (doing what the errors say to do), but I don't know if that is detrimental to overall performance.

after set the env:TOKENIZERS_PARALLELISM=true and GRPC_VERBOSITY=“NONE” the error disapper,but the chat response is not normal
image
Screenshot 2024-12-12 at 2 46 17 PM

@AlexCheema
Copy link
Contributor

Not entirely sure when this was introduced. I can reproduce the issue so I will investigate and push a fix.

@jamesmcn
Copy link

jamesmcn commented Dec 16, 2024

I'm also encountering the fork() error and bizarre output once the web interface fully loads. 64GB M1Max Studio + 24GB M3MBA.

Edit:
Unclear if setting TOKENIZERS_PARALLELISM=true and GRPC_VERBOSITY=“NONE” fixed the bizarre output or if it was something else. I still get a constant stream of fork() errors logged to the screen on both machines.

@OhJayGee
Copy link

can reproduce here as well.
Additionally: no answers from lama-3.3-70b.
Unsure If that is because of the errors above, or something particular about lama-3.3
environment: macOS 15.2 on M2Max 32G + M4Pro Mini 24G

@cadenmackenzie
Copy link
Contributor

Also can reproduce error. I believe it was first introduced here.

@smokk89
Copy link

smokk89 commented Dec 19, 2024

seeing the exact same error as well

@rogerc66
Copy link

rogerc66 commented Dec 25, 2024

I'm having the same issue with mac mini 24G.

For my case, both mac mini can see each other, but they spam the message non-stop.

@yaomogumq
Copy link

reproduced the error in macbook pro M4 max . Also when connecting the current macbook to macbook pro m1 max. The old mac can see the bridging while the new one cannot see the bridging in the terminal.

@pepebruari
Copy link

pepebruari commented Dec 31, 2024

Run export GRPC_VERBOSITY=ERROR && export TOKENIZERS_PARALLELISM=false before running exo and you won't see the warnings repeat.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants