AL Extension leaves Microsoft.Dynamics.Nav.EditorServices.Host processes behind after closing VSCode

1. Describe the bug
On MacOS the "Microsoft.Dynamics.Nav.EditorServices.Host" processes opened by VSCode are not being closed when VSCode is closed resulting orphaned processes actively using RAM

2. To Reproduce
Steps to reproduce the behavior:

1. Start VSCode
2. Open a workspace or directory containing AL extension(s)
3. Wait the project to load
4. Close VSCode
5. The "Microsoft.Dynamics.Nav.EditorServices.Host" process is never closed
6. Repeat steps 1-5 and observe the growing number of orphaned processes

3. Expected behavior
The "Microsoft.Dynamics.Nav.EditorServices.Host" processes are being closed with VSCode

4. Actual behavior
The "Microsoft.Dynamics.Nav.EditorServices.Host" processes are not being closed with VSCode

5. Versions:

• AL Language: 17.0.2273547
• Visual Studio Code:
  Version: 1.116.0
  Commit: 560a9dba96f961efea7b1612916f89e5d5d4d679
  Date: 2026-04-15T00:28:13Z (1 day ago)
  Electron: 39.8.7
  ElectronBuildId: 13797146
  Chromium: 142.0.7444.265
  Node.js: 22.22.1
  V8: 14.2.231.22-electron.0
  OS: Darwin arm64 25.5.0
• Business Central: Not relevant
• List of Visual Studio Code extensions that you have installed: AL, Create GUID, PowerShell, Dracula Theme
• Operating System:
  • Windows
  • Linux
  • MacOS (26.5 Beta (25F5042g))

Final Checklist

Please remember to do the following:

• Search the issue repository to ensure you are reporting a new issue

• Reproduce the issue after disabling all extensions except the AL Language extension

• Simplify your code around the issue to better isolate the problem

Internal work item: AB#634183

Reproduce the issue on macOS by opening a workspace with AL extensions in VSCode, closing VSCode, and checking for Microsoft.Dynamics.Nav.EditorServices.Host processes. Trace the AL extension's process startup and shutdown handling; done means those processes terminate when VSCode closes and repeated sessions do not leave additional orphaned processes.