Symptom: You encounter this error message: "extension host terminated unexpectedly 3 times within the last 5 minutes".
Possible Causes: This is usually caused by a memory leak. First use the extension bisect method to confirm whether the crash is caused by Lingma.
Solution: If you confirm it is caused by Lingma, resolve it using the following methods:
If the problem persists, join the DingTalk group: 53770000738, and provide the following information:
Operating system version and VS Code version.
Collect and provide verbose logs:
Completely exit VS Code.
Run the command code --verbose
to start VS Code.
Perform the operation that causes the crash.
Check the output logs. Lines 2 and 3 will give the preliminary reason for the crash, which helps technical staff locate the code in Lingma more quickly. For example:
[main 2025-05-02T14:35:31.249Z] [UtilityProcess id: 3, type: extensionHost, pid: 25816]: received exit event with code 18446744072635810000
[main 2025-05-02T14:35:31.249Z] Extension host with pid 25816 exited with code: 18446744072635810000, signal: unknown.
[main 2025-05-02T14:35:31.250Z] [UtilityProcess id: 3, type: extensionHost, pid: 25816]: crashed with code -1073741819 and reason 'crashed'
[19684:0502/223531.251:INFO:CONSOLE(3255)] "Extension host (LocalProcess pid: 25816) terminated unexpectedly. Code: 18446744072635810000, Signal: unknown", source: vscode-file://vscode-app/d:/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js (3255)
If the above logs cannot confirm that the code in Lingma is causing the issue, refer to Native-Crash-Issues to collect more detailed crash logs. Here're the steps:
Completely exit VS Code.
Run the command code --crash-reporter-directory <absolute path>
.
Perform the operation that causes the crash.
Look for a file with a .dmp
extension in the directory from step 2, and send it to the technical team.