Autocomplete working sporadically

[AshleyFinney]

Description

Since about 3 days ago (15/05/17) autocomplete is working sporadically. It will work for a few seconds then stops working for a few minutes then starts working again, all in the same Atom session. The only things I've changed since it stopped working are updating 'go-plus' and 'linter-ui-default'. I've run 'golang:update-tools' to make sure I'm up to date but still no luck.

Output from atom -v && apm -v

Atom : 1.17.0 Electron: 1.3.15 Chrome : 52.0.2743.82 Node : 6.5.0 apm 1.17.0 npm 3.10.5 node 6.9.5 ia32 python git 1.9.0.msysgit.0 visual studio 2013

Output From go env

$ E:\gae\go_appengine\goroot\bin\go.exe version go version go1.6.3 windows/amd64

$ E:\gae\go_appengine\goroot\bin\go.exe env set GOARCH=amd64 set GOBIN= set GOEXE=.exe set GOHOSTARCH=amd64 set GOHOSTOS=windows set GOOS=windows set GOPATH=E:\GoWork set GORACE= set GOROOT=E:\gae\go_appengine\goroot set GOTOOLDIR=E:\gae\go_appengine\goroot\pkg\tool\windows_amd64 set GO15VENDOREXPERIMENT=1 set CC=gcc set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 set CXX=g++ set CGO_ENABLED=1

Steps to Reproduce

1. Program as normal, autocomplete works.
2. Program as normal, autocomplete doesn't pop up.
3. Program as normal, autocomplete works again.

[joefitzgerald]

I've also noticed some strangeness (I use diagnostics as my UI) and had attributed it to the UI but now this makes me think it's something else.

I am sorry you are having this issue!

Could you hop on Slack and ping me when you are experiencing the issue, so that we might be able to do a screen sharing session?

[silverkorn]

I have similar issues but my entire explorer.exe process (Windows' taskbar) is killed... Experimented on Atom 1.16.0 x64 & 1.15.0 x64 on 2 different Windows 7 Pro SP1 machines and seems to happen mostly while saving, but not always... It's hard to pinpoint. I've had this kind of problem since my first installation on January 2017 and go-plus updates never fixed the issue...

[Zamiell]

It sounds like I have exactly the same problem as @silverkorn - for about a year now, go-plus has caused random programs on my computer to just randomly close/crash, including Discord, Skype, and explorer.exe, which causes me to have to Ctrl+Alt+Del, select Task Manager, File --> New Task, and reopen explorer.exe. It is super annoying and sometimes happens every 5 minutes or so while working on some Go code. (I constantly save as I work, which causes all of the builds to kick off, which I assume causes the crashing.)

For reference, I am on Windows 7 Professional.

[joefitzgerald]

@Zamiell go-plus causing other programs to crash seems to defy logic. I'm not dismissing it, but fundamentally that would mean that Windows' process isolation is broken, which seems unlikely. An alternative theory is that this is somehow due to a) memory use or b) filesystem use.

go-plus is just invoking other processes (e.g. go itself, gocode, gometalinter, etc.). Is there any way to reliably reproduce this behavior?

[Zamiell]

It seems to happen completely randomly as I code, once every 10 minutes or so. I think it will be hard to reproduce it exactly, because the follow sequence of events happens:

• I press "Ctrl+s" to save the file
• go-plus runs some programs and explorer.exe crashes (my taskbar completely disappears)
• I restart explorer.exe through "Ctrl+Alt+Delete" + Task Manager
• I press "Ctrl+s" to save the file again, and explorer.exe doesn't crash.

I'm open to suggestions for reliable ways to reproduce; your guess is as good as mine, and I'd also be willing to submit additional logs or submit to a screen-sharing session. But it looks like at least 3 people are getting this problem on a Windows machine, so I'm inclined to think it is a general Windows problem with go-plus and/or the tools it invokes.

[Zamiell]

Furthermore, I've been programming some on macOS, and I occasionally get this:

I have the most recent version of Go and the most recent version of gocode (and the most recent version of go-plus), so the error message isn't very helpful. But what is interesting is that I am working on the same code that crashes my Windows box, so perhaps it is my code that is somehow causing the Windows crash / the macOS panic. Although that is just pure speculation and not necessarily related.