AL Extension leaves Microsoft.Dynamics.Nav.EditorServices.Host processes behind after closing VSCode
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- vscode
- Domain
- tooling
Research direction
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.
Written by the indexing model from the issue text.
Description
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:
- Start VSCode
- Open a workspace or directory containing AL extension(s)
- Wait the project to load
- Close VSCode
- The "Microsoft.Dynamics.Nav.EditorServices.Host" process is never closed
- 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
- Dominant language
- PowerShell
- Stars
- 881
- Forks
- 285
- Avg merge
- 3d 36m
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/AL
-
accepted al-tools bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
AL 18.0.2732683 regression: System.Drawing types cannot be resolved from assembly probing paths Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
accepted packaging
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
hemilabs/ui-monorepo#2332 ·
-
Help-Wanted Needs-Triage Package-Update
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/winget-pkgs#438662 ·
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
olcf/olcf-test-harness#278 · 1 comment ·