-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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.
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
The Microsoft.VSCode.CPP.IntelliSense.Msvc.linux process hangs #912
Comments
How long does it get stuck using lots of CPU? High CPU usage is normal for the process, which does compiling. Can you attach a debugger and/or get a core dmp? Does it hang with a simple workspace with a single C++ file? |
Always, until I kill the process.
No. |
I'm having the exact same issue. "Loading" in the editor, "Parsing" in the status bar. Processes sitting at FUTEX_WAIT_PRIVATE. Ubuntu 16.04.2 LTS. |
Attached is a core dump. I haven't done that before so let me know if it's what you need.
|
@Cerh It looks like the parser might be in an infinite loop in Thread 3 -- the call stack is cut off for that thread, so can you include a full one? Also can you provide additional thread call stack for that thread (i.e. a thread that isn't blocked on a wait) so I can compare them, i.e. to help narrow down which function is infinite looping. If you can provide a repro project that exhibits this infinite loop that would be great too. We have never seen this infinite looping before in the IntelliSense process. |
@thomashw Your issue appears different (not an infinite processing loop). Can you get a core dmp to show all the thread call stacks? I don't appear to be able to get any call stacks from the core dmp using gdb with bt. |
I can add only the сore dump of this process. |
Let me know if you need anything else.
|
Same issue on Ubuntu 16.04 |
I can confirm the same issue on Fedora 26 |
The high CPU issue could be a known infinite loop that can occur when parsing certain code(#981 ). For the deadlock, the call stacks and dmps have so far not been helpful. Can anyone provide an actual repro with some open source project and/or with the actions that triggers it and/or attaching some logs or sending them to [email protected] (see https://github.com/Microsoft/vscode-cpptools/blob/master/Documentation/LanguageServer/Enabling%20logging.md ). |
I see this too, the processes don't die after closing VSCode, so they build up until I kill them. OS: Ubuntu 16.04. About VSCode: Unfortunately I am working with a proprietary codebase. |
I was able to discover a cause of lingering processes on linux/mac and we'll release an update this week with that fix. I haven't solved all of the "futex_wait" issues, but the yet-to-be-released version of the extension is running much more reliably for me on Ubuntu right now. |
Our preview .vsix might fix this -- instead of sending a shutdown request on exit, we just terminate the IntelliSense processes: https://github.com/Microsoft/vscode-cpptools/releases/tag/v0.15.0-insiders (the final release is planned for next week). We fixed the crash with source_file_for_seq too. |
Ubuntu 16.04. C_Cpp.intelliSenseEngine=Default. Tooltips in the editor write "Loading ...", in the status bar "Parsing ...".
The text was updated successfully, but these errors were encountered: