You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I am seeing the following in htop (but also in other places) havin goenv on my M1 MacBook:
That keeps basically running all the time, sometimes there is even more than one instances consuming multiple CPU cores.
Killing the process doesn't really help as it gets restarted.
goenv-version-file seems to get (re-)started by goenv-version-name which again gets started by goenv-sh-rehash --only-manage-paths.
Following the chain further up probably isn't too helpful but it looks like goenv's initial invocation comes from zsh (probably looking for the current dir's Go version as I have enabled showing it in powerlevel10k), which gets started by some macOS system update component (which, indeed, seems to be stuck - so that would make sense).
Any idea why goenv-version-file keeps on searching without ever coming to an end?
The text was updated successfully, but these errors were encountered:
I don't exclude the possibility of this being a bug, I haven't personally hit it before.
Hmm, do you have a bit more to show from your .zshrc? Looking for a loopy bootstrap logic.
Hello,
I am seeing the following in
htop
(but also in other places) havingoenv
on my M1 MacBook:That keeps basically running all the time, sometimes there is even more than one instances consuming multiple CPU cores.
Killing the process doesn't really help as it gets restarted.
goenv-version-file
seems to get (re-)started bygoenv-version-name
which again gets started bygoenv-sh-rehash --only-manage-paths
.Following the chain further up probably isn't too helpful but it looks like
goenv
's initial invocation comes fromzsh
(probably looking for the current dir's Go version as I have enabled showing it inpowerlevel10k
), which gets started by some macOS system update component (which, indeed, seems to be stuck - so that would make sense).Any idea why
goenv-version-file
keeps on searching without ever coming to an end?The text was updated successfully, but these errors were encountered: