OS X, 0.16.1 C/C++ Extension , VS Code 1.22
Intellisense Seems to work when VS Code is launched at the beginning, and always pretty soon
it hangs it self up ->
Shutting down IntelliSense server: ...ExecutionGraph/gui/executionGraphGui/cefapp/App.cpp
Failed to create IntelliSense client. No args provider
Checking for syntax errors: ...ExecutionGraph/gui/executionGraphGui/backend/BackendRequestHandler.cpp
Shutting down IntelliSense server: ...gui/executionGraphGui/cefapp/BackendResourceHandler.cpp
Failed to create IntelliSense client. No args provider
At this point nothing works anymore, formatting, code completiong...
Does anybody know where the problem is? What does no args provider mean?
That's a bug. I can't think of how it's possible to get into this state, but we'll have to take another look at the code. Does reloading the window fix it? Does IntelliSense work for a while and then quit?
The args provider is just the object we use to aggregate arguments to send to the IntelliSense compiler.
Reloading the window does not fix it, although Intellisense starts parsing again...
I have not found the way to reproduce it consistently. It seems that while looking up a definition or a symbol which is not parsed, Intellisense starts to dig, the blue progress bar moves along the top of the window and nothing happens anymore.
but that might be a very wrong guess...
Am 01.05.2018 um 19:34 schrieb Bob Brown notifications@github.com:
That's a bug. I can't think of how it's possible to get into this state, but we'll have to take another look at the code. Does reloading the window fix it? Does IntelliSense work for a while and then quit?
The args provider is just the object we use to aggregate arguments to send to the IntelliSense compiler.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/Microsoft/vscode-cpptools/issues/1908#issuecomment-385734012, or mute the thread https://github.com/notifications/unsubscribe-auth/AAnhDUdD6p_EXgw4Jm1gJa0qZWdWlO7Tks5tuJypgaJpZM4TuOLG.
I believe I found the root cause of this today.
This is so good to hear!
@bobbrow share with us your suspicion
I could, but it probably wouldn't make sense since you don't have access to the code in question. It looks like a boolean's intent got inverted when we made the fix to link header file changes to all translation units referencing them.
Thanks for sharing it
Should be fixed with 0.17.5.
Most helpful comment
I believe I found the root cause of this today.