Memory leak when running debugger through

[ynain]

Checklist

• The issue is about this extension and NOT about a fork.
• Check the known issues list.
• The latest version of the extension was used.
• It is not related to remote-vscode or I checked the following issue
• Imagine yourself into my position and think how hard to debug the issue without insufficient information.
  I understand that you have privacy concerns and I expect you to understand that this extension is developed for free.
  Thanks.

Describe the bug

When using C++ std library containers (but especially the std::vector, the debugger hangs indefinitely, and never resumes until the process is stopped. Even after this, the lldb-mi process will continue to run and will continue consuming memory until it is force stopped.

To Reproduce

Exactly the same issue as described here: microsoft/vscode-cpptools#10176

Screenshots (optional)

Hanging indefinitely:

Increased memory consumption within seconds:

After force stopping, the debugger in vscode fails.

Desktop

• Extension Version: 4.3.12
• VS Code Version: 1.76.2
• Catch2 / Google Test / DOCTest Version: Google Test 1.12.0
• OS Type and Version: MacOS 13.2.1
• Using remote-ssh/docker/wsl?: No

Regression bug?

• Last extension version in which the feature were working:

Log (optional but recommended)

Example logs are defined in the issue linked previously: microsoft/vscode-cpptools#10176

[matepek]

Hello,
This extension does not come with the debugger. It uses other vscode debugger extensions.
Therefore this issue is most likely unrelated.

[ynain]

Are we able to change the debugger that the extension is using? I am able to temporarily rectify the issue by using CodeLLDB as described here. microsoft/vscode-cpptools#7240 (comment)

[matepek]

I recommend reading the documentation of this extension. Start with the README.md