Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Sometimes it takes unusual longtime or forver to find definitions with C/C++ Extensions #2119

Closed
RogFedex opened this issue Jun 11, 2018 · 4 comments
Closed

Sometimes it takes unusual longtime or forver to find definitions with C/C++ Extensions #2119

RogFedex opened this issue Jun 11, 2018 · 4 comments
Labels
bug duplicate Language Service performance

Comments

@RogFedex
Copy link

With C/C++ Intellisense extension, it takes long time or even hangs to go to defintion or when finding definitions. If we reload vscode and search again then it finds definition immediately.
@RogFedex RogFedex changed the title Sometimes it taked unusual longtime or forver to find definitions Sometimes it takes unusual longtime or forver to find definitions with C/C++ Extensions Jun 11, 2018
@sean-mcmanus
Copy link
Contributor

Is there a red flame in the bottom right when it hangs on Go to Definition? It could be the same as #1928 .

If you can attach a debugger and get call stacks, that would show exactly what it's stuck on.

@sean-mcmanus sean-mcmanus added bug Language Service more info needed The issue report is not actionable in its current state performance labels Jun 11, 2018
@RogFedex
Copy link
Author

RogFedex commented Jun 11, 2018 •
edited
Loading

Ok. It sounds same as #1928. Do i need to change my setting - "C_Cpp.intelliSenseEngine" as temporary workaround ?

@sean-mcmanus sean-mcmanus removed the more info needed The issue report is not actionable in its current state label Jun 11, 2018
@sean-mcmanus
Copy link
Contributor

You can if you want, but using the "Tag Parser" will have fewer features enabled. You might also want to make sure your includePath doesn't have "**" in it, in case that is causing the performance issues (which was somewhat fixed by https://github.com/Microsoft/vscode-cpptools/releases/tag/v0.17.5-insiders ).

@bobbrow
Copy link
Member

bobbrow commented Jul 20, 2018

Closing as duplicate of #1928. Thank you for the feedback.

@bobbrow bobbrow closed this as completed Jul 20, 2018
@github-actions github-actions bot locked and limited conversation to collaborators Oct 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug duplicate Language Service performance
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@bobbrow @sean-mcmanus @RogFedex