Ycmd crashes without any error messages.

Question

Ycmd crashes without any error messages.

Closed this issue 7 years ago · 10 comments

As it says in the title, I can't get ycmd to work on my projects.

Maybe these lines from the Messages buffer are relevant:

gui-get-primary-selection: No selection is available
Ycmd server killed
ERROR: Ycmd server timeout

An interesting fact is that it can be used if I restart it with ycmd-open.

I am using the latest version installed by Spacemacs.

Answer 1 · 2017-02-27T15:56:26.000Z

I'm not sure why you might be seeing this, but it seems to be coming from select.el. Can you use stack-trace-on-error or debug-on-error to see the context in which this is happening?

Answer 2 · 2017-02-27T16:07:35.000Z

It seems to be unrelated.
It happens if I open the file by clicking on it in the home screen. If I press RET it doesn't show up.

Answer 3 · 2017-02-27T16:21:02.000Z

So this happens when you start emacs and click on a file from the *spacemacs* buffer's "Recent Files" list?

What does the *ycmd-server* buffer show?

Answer 4 · 2017-02-27T16:25:43.000Z

ycmd crashes no matter how I open the file. If I open it with the mouse the GUI selection error appears. The ycmd-server buffer is empty Il 27/feb/2017 01:21 PM, "abingham" <notifications@github.com> ha scritto:

…

So this happens when you start emacs and click on a file from the *spacemacs* buffer's "Recent Files" list? What does the *ycmd-server* buffer show? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#401 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AC9n6l0hrMmZCh37oAGyjowD04HO_tkKks5rgvfugaJpZM4MNO-g> .

Answer 5 · 2017-02-27T16:36:53.000Z

Hmmm...does ycmd-show-debug-info show anything that looks useful?

Answer 6 · 2017-02-27T16:39:55.000Z

No debug info available from server

Server is not running

Ycmd Mode is enabled

Ycmd version: 1.1snapshot (package: 20170114.445)
Emacs version: 25.1.1
System: x86_64-w64-mingw32
Window system: w32

Answer 7 · 2017-02-27T20:05:23.000Z

I found a workaround: setting ycmd-startup-timeout to 10 seems to fix the problem.

Answer 8 · 2017-02-27T21:35:29.000Z

OK, good, that was kind of thing I was going to suggest you look at next. Can I go ahead and close this, or do you think there's more to do?

…

On Mon, Feb 27, 2017 at 8:05 PM nicber ***@***.***> wrote: I found a workaround: setting ycmd-startup-timeout to 10 seems to fix the problem. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#401 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAE1eEJc0VgEdUcKzcdcxU7vvjJewLzbks5rgyyDgaJpZM4MNO-g> .

Answer 9 · 2017-02-27T21:47:20.000Z

Maybe the timeout can be longer by default to avoid similar issues?

Answer 10 · 2017-02-28T07:44:34.000Z

A longer timeout might be the right way to go, but I don't want to do that until/unless we get more reports of similar problems. Yours is the first that I know of.

What I have done, though, is added some text to the error message printed when a timeout occurs. Now is tells users that that they might need to increase the value of ycmd-startup-timeout. Thanks for working with us on this!