You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Creating an implementation of a member function sometimes causes C++ features to break, in general. For example, the Problems tab no longer updates; existing errors remain highlighted even if I add or remove lines of code.
I know very little about reporting these kinds of issues, but I did see this in the Window log:
[2022-02-16 14:31:46.882] [renderer1] [warning] UNRESPONSIVE extension host, 'amiralizadeh9480.cpp-helper' took 100% of 5062.333ms, saved PROFILE here: 'file:///var/folders/tf/62gdm4xx4bddtyz106q__5340000gn/T/exthost-cdeae8.cpuprofile' [{"id":"amiralizadeh9480.cpp-helper","total":5062208,"percentage":100}]
I believe this started after the update from two days ago. I am running on MacOS Monterey. I tried removing and reinstalling the extension, but the behavior is the same.
It's not a consistent problem. I tried to reproduce it with a simple example and failed, but just had it happen again a few minutes ago.
Let me know what diagnostics I should be looking for!
The text was updated successfully, but these errors were encountered:
Etherealflux
changed the title
Creating an implementation sometimes breaks C++ the language server?
Creating an implementation sometimes breaks the C++ language server?
Feb 16, 2022
I noticed this happening when attempting to create an implementation and the source file can't be found/created. For me, it broke the Vim plugin and basically just ignored all my key strokes. The editor is essentially locked out until I restart.
Creating an implementation of a member function sometimes causes C++ features to break, in general. For example, the Problems tab no longer updates; existing errors remain highlighted even if I add or remove lines of code.
I know very little about reporting these kinds of issues, but I did see this in the Window log:
I believe this started after the update from two days ago. I am running on MacOS Monterey. I tried removing and reinstalling the extension, but the behavior is the same.
It's not a consistent problem. I tried to reproduce it with a simple example and failed, but just had it happen again a few minutes ago.
Let me know what diagnostics I should be looking for!
The text was updated successfully, but these errors were encountered: