lldb-mi hangs and starts consuming more and more memory when stopping at certain breakpoints in vscode-cpptools

[mlangiu]

Hi, I wanted to notify you of several issues that crop up with debugging via the cpptools package for Visual Studio Code, which appear to be caused by an error in lldb-mi.
In summary stopping at (or in some cases near) uninitialized memory.
More details can be found in the following related issues

• lldb-mi becomes unresponsive, uses lots of memory microsoft/vscode-cpptools#1899
• LLDB debugger hangs (using 100% cpu) at launch if std::map is uninitialised  microsoft/vscode-cpptools#5805
• lldb-mi freezes on MacOS when breaking near uninitialised variables microsoft/vscode-cpptools#7240

Kind Regards

Marco

[alexolog]

One year later, the problem still exists

[wl2776]

Almost 2 years have passed, the issue is still here.

[mattkanwisher]

having same issue, I can get it to use 80gb of ram and wreck a 96gb ram laptop for a program that usually uses 300 meg of ram

[sunshaoce]

microsoft/vscode-cpptools#7240
Here seems to be a feasible solution, can any Mac users help test it out?

[samuelbodin]

experiencing the same issue now...