Open mvgijssel opened 2 years ago
Very strange. Have you added anything to your Dotfiles in Fig?
Very strange. Have you added anything to your Dotfiles in Fig?
Yes! Just some basic environment variables and aliases.
these are my installed plugins
Interestingly enough if I disable all the plugins and run fig source
the terminal isn't actually updated 🤔. Killing the terminal and opening a new one also doesn't seem to help. For example if I disable the Pure
prompt, it still shows up after sourcing and restarting the terminal.
Also validated that if I remove the following statements from .zshrc
and .zprofile
both iTerm and Terminal are back to normal working condition
# .zprofile
[[ -f "$HOME/.fig/shell/zprofile.pre.zsh" ]] && builtin source "$HOME/.fig/shell/zprofile.pre.zsh"
[[ -f "$HOME/.fig/shell/zprofile.post.zsh" ]] && builtin source "$HOME/.fig/shell/zprofile.post.zsh"
# .zshrc
[[ -f "$HOME/.fig/shell/zshrc.pre.zsh" ]] && builtin source "$HOME/.fig/shell/zshrc.pre.zsh"
[[ -f "$HOME/.fig/shell/zshrc.post.zsh" ]] && builtin source "$HOME/.fig/shell/zshrc.post.zsh"
Running the "Uninstall Fig" script and re-installing also doesn't help, still remains painfully slow.
Changing ~/.zshrc
and ~/.zprofile
to be actual files instead of symlinks also didn't help.
Using the Fig UI is also pretty sluggish, not sure if that is related to this problem. Though because it feels like the problem started happening out of the blue and the way it is slow, it might suggest that Fig is doing blocking outbound calls.
I am running into the same issue too, opening and closing tabs in iTerm gave me a rainbow wheel for about 10 seconds or so.
One thing I did notice is that it happens when opening tabs where the initial tab had quite a bit of history (from yarn install logs, git clones, creating/removing directories). I have iTerm set up to maintain the login session when opening tabs, so it stays in the current folder when I split the terminal etc.
After closing all my tabs and opening fresh ones, it seems to have resolved itself.
Hopefully that info helps you narrow down the issue
Hey @mvgijssel, sorry about the inconvenience here.
Can you run this command to disable any Dotfiles blocks or plugins from being sourced in new terminal sessions and see if the issue goes away?
fig _ local-state dotfiles.enabled false
Also by chance have you started using BlockBlock? I just was on a debugging call with a user who reported slow terminal startup times and this was the culprit.
Hey @mvgijssel, sorry about the inconvenience here.
Can you run this command to disable any Dotfiles blocks or plugins from being sourced in new terminal sessions and see if the issue goes away?
fig _ local-state dotfiles.enabled false
Also by chance have you started using BlockBlock? I just was on a debugging call with a user who reported slow terminal startup times and this was the culprit.
Sorry for the late reply! But running that statement made performance even worse 😅. I'm not using BlockBlock as far as I know!
Same problem😭 Does anyone have a solution?
same issue here
Updated Fig and macOS to the latest version
❯ fig version
fig_cli 2.7.9
❯ sw_vers
ProductName: macOS
ProductVersion: 13.0.1
BuildVersion: 22A400
But unfortunately this did not resolve it, maybe even made it a little bit slower 😅.
Sanity checks
fig doctor
in the affected terminal sessionfig restart
and tested again (tell us if that fixed it)Issue Details
Description:
Not sure what changed, but starting today whenever I open a new terminal, new terminal tab or do basic terminal usage it seems to be sluggish either using Terminal or iTerm. When I start a new iTerm session it also looks to be stuck on the
fig
process. Starting a window this way went from ~1 second to ~30 seconds looking like this:Environment