withfig
Unusual High CPU usage “fig-darwin-universal”
Description:
Even if I don't open any terminals, the process will continue to take up a lot of operation after a period of time. When I quit fig, the process still runs.
Details:
| macOS | Fig | Shell |
|---|---|---|
| 12.6.0 | Version 1.0.62 (B542) | /bin/zsh |
fig diagnostic
Version 1.0.62 (B542) [ABC] UserShell: /bin/zsh Bundle path: /Applications/Fig.app Autocomplete: true Settings.json: true CLI installed: true CLI tool path: /Users/daikaiyu/.fig/bin/fig Accessibility: true SSH Integration: false Tmux Integration: false iTerm Integration: false Hyper Integration: true VSCode Integration: true Docker Integration: false Symlinked dotfiles: false Only insert on tab: false UNIX Socket Exists: true Installation Script: true PseudoTerminal Path: /Users/daikaiyu/.nvm/versions/node/v16.17.0/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/daikaiyu/.fig/bin:/Users/daikaiyu/.local/bin:/Users/daikaiyu/.nvm/versions/node/v16.17.0/bin SecureKeyboardInput: false SecureKeyboardProcess:Current active process: ??? (???) - ??? Current terminal session: ??? Current working directory: ??? Current window identifier: ???
This is our background daemon which syncs your Dotfiles & Setting. It definitely should not be using this much CPU. Can you running fig restart daemon? cc @grant0417
@mschrage fig restart daemon resolves this issue. But I still didn't know why it happened.
An old bug would deadlock one of our threads. This should be resolved but let me know if you encounter this again!
happened with me today (on macbook pro intel) — caused overheating. I have not even been using fig since quite a long time. Fig menu bar app was NOT open.
I am having issues with this too. Even with fig closed - the daemon seems active and is burning through my battery. Constantly causing it to overheat, draining it when it should be asleep 😢
Can confirm this happened too. Over 60% CPU usage on Macbook with Intel. Restarting the daemon solved it but I had not used it in a long time either.
I experienced this issue today immediately after a restart following an OS update. The restart fixed the problem. I am also using an Intel based iMac now running Ventura 13.6.5. I didn't have terminal open until I opened one to restart the fig daemon.
This high CPU usage by fig-darwin-universal kept recurring every hour or so. I could temporarily reduce the usage to normal levels by restarting the daemon, but it would start using all of one CPU core again in about an hour. I had to uninstall fig to eliminate the high CPU usage.
Just experienced this issue after updating my Mac mini M1 - started at 102% for a while then went to 42%, the restart fixed it.
