-
Notifications
You must be signed in to change notification settings - Fork 645
Performance is down after upgrading to macOS Sierra. #503
Comments
+1 I also have this issue. Didn't start for me until I updated to Macos Sierra. Please don't make me switch to Sublime 😢 |
I started using sublime again because of this and it makes me really sad as well. |
godef 63.7 CPU |
I'm experiencing something similar, multiple godoc processes, each one consuming ~45% of CPU |
I have to go and constantly kill the process with the activity monitor |
Are folks who are seeing this using Go 1.6 or earlier? Looks like there is a serious issue with Go pre-1.7 on Sierra that are likely related. |
I'm using Go 1.7 |
go 1.7.1 |
go version go1.7 |
go 1.7.1 |
I think I've discovered the cause of the error. Go needs to be recompiled from source to work with Sierra. Specifically, the gotools to fix this issue. To fix this, I took go's 1.4.3 source, compiled it using the cherry-picked suggestions from the issue (it fails some tests, but works fine as a bootstrapper) and the recompiled 1.7.1 using that newly compiled 1.4.3 bootstrapper. This completely fixed this issue for me. |
Sadly, I have to report that there are less godefs running, but it didn't completely eliminate the problem. |
Brew upgrading 1.6 > 1.7.1 reduced the number of orphaned go/godef/gocode instances running by a lot, but left one residual go instance running at ~68% CPU on a MBPR. On battery this turning the typical 8hr experience into ~60mins of lap warming. |
I have a friend that uses Atom and he is having similar issues, so it might be something with the Go tools themselves. |
I had the same problem after upgrading to Sierra and go1.7. I reinstalled every tool (godef, goreturns etc) and the issue was gone. The old compiled binaries aren't 100% compatible with Sierra. |
@tecbot did the same and worked! 👍 |
@tecbot Great to hear. Hope that this solves others' problems as well. @troylelandshields Yes, this issue isn't going to be specific to VSCode - it's a problem with Go and the Go tools that are used by the editor extensions. I expect users of any editor which uses these tools will have similar issues. |
@tecbot could you explain exactly how you did that. Thanks |
@q45 just use this snippet, if you have other gotools that also use 100% CPU, just update them like this.
|
You could also run the command |
Closing this as re-installing all the Go tools solves the problem. If anyone still sees this issue with Go 1.7 and Sierra, please feel free to re-open this issue |
hmm could it be there are also issues with go get itself?
go env
GOARCH="amd64"
GOBIN="/Users/gert/go/bin"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/gert/go"
GORACE=""
GOROOT="/usr/local/Cellar/go/1.7.1/libexec"
GOTOOLDIR="/usr/local/Cellar/go/1.7.1/libexec/pkg/tool/darwin_amd64"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/dv/8tlwvjr91zjdyq4rk14lkkfm0000gn/T/go-build584711619=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
CGO_ENABLED="1"
|
never mind removing |
@ramya-rao-a hi , i just ran into this problem. It is embarrassing to say but i really can't find where to run the command. |
@archerbj Not a problem at all. You need to run the command from the command pallet. So
|
@ramya-rao-a Thanks a lot ! |
I recently encountered this issue after upgrading to MacOS Sierra. Why can the extension not notify the users to run As a user I'd like the editor/plugin to either solve these issues by itself or to notify me what I can do to solve it. |
Users don't need to update the tools every time an update is available. One thing we can do is to prompt to update when the Go version used by the user changes. Any other ideas? |
Hmm I personally would leave it as it is and just point it out in the docs. Also please create a new issue for it if you believe it needs to be a new feature. |
@ramya-rao-a I would appreciate the prompt as I constantly switch my Go version underneath when testing new Go releases and it breaks vscode every time. |
Seems like after opened for awhile godef and golint really ramp up on CPU.
The text was updated successfully, but these errors were encountered: