Aura Language Server Holding Open `customLabels.d.ts`

[justin-lyon]

Summary

When I open VSCode the .sfdx/typings/lwc/customlabels.d.ts files is held open. The file appears to be edited and the text is flickering on screen. When I try to close the vscode tab, with and without saving, the tab is reopened in the edited state.

When I reloaded the window (CMD+P: Developer: Reload Window) I noticed it started after the Aura Language Server started popup. When I disable the Aura Components extension the error stops.

Steps To Reproduce:

1. Open VSCode with Salesforce Extension Pack.
2. Wait for Aura Language Server to start.
3. Verify that the .sfdx/typings/lwc/customlabels.d.ts file is open and edited.
4. Close the customlabels.d.ts file.
5. Verify that the file is reopened.
6. Disable the Aura Components vscode extension.
7. Reload the VSCode Window
8. Close the customlabels.d.ts file.
9. Verify that the file does not open again.

Expected result

Aura Language Server should not open files in my editor.

Actual result

Aura Language Server appears to open and edit a file repeatedly in my vscode editor. I cannot close the file and it causes screen flickering.

Additional information

Screen.Recording.2026-02-02.at.9.25.13.AM.mov

Salesforce Extension Version in VS Code:
65.15.2

Salesforce CLI Version:
@salesforce/cli/2.120.3 darwin-arm64 node-v22.9.0

OS and version:
mac os 13.3.1 (a) (22E772610a

VS Code version:
1.108.2

Most recent version of the extensions where this was working:
I don't know.

[svc-idee-bot]

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

[juanmtriguero]

This is also happening to me, it's very annoying

[ssisaias]

Also happening here.
Logs for the language server look normal:
11:39:18.949 [Apex Prelude Service STARTING] INFO a.j.l.i.s.ApexPreludeManagedService - Scanning built-in and system Apex types.
11:39:18.979 [Apex Prelude Service STARTING] INFO a.j.l.i.s.ApexPreludeManagedService - Scanning built-in Apex types.
11:39:18.982 [Apex Prelude Service STARTING] INFO a.j.l.i.s.ApexPreludeManagedService - Collecting built-in standard types from jar
11:39:19.511 [Apex Prelude Service STARTING] INFO a.j.l.i.s.ApexPreludeManagedService - Done collecting built-in standard types from jar
11:39:19.512 [Apex Prelude Service STARTING] INFO a.j.l.i.s.ApexPreludeManagedService - Scanning Apex Standard Library.
11:39:19.753 [Apex Prelude Service STARTING] INFO a.j.l.i.s.ApexPreludeManagedService - Done scanning Apex Standard Library.
11:39:19.755 [Apex Prelude Service STARTING] INFO a.j.l.i.s.ApexPreludeManagedService - Starting ApexIndexer.
11:39:19.763 [ApexIndexer STARTING] INFO a.jorje.lsp.impl.index.ApexIndexer - ApexIndexer: Start indexer.
11:39:19.769 [ApexIndexer STARTING] INFO a.jorje.lsp.impl.index.ApexIndexer - ApexIndexer: Scanning user-defined types.
11:39:19.770 [ApexIndexer STARTING] INFO a.jorje.lsp.impl.index.ApexIndexer - ApexIndexer: Scanning workspace source.
11:39:20.310 [ApexIndexer STARTING] INFO a.jorje.lsp.impl.index.ApexIndexer - ApexIndexer: Building change list.
11:39:20.805 [ApexIndexer STARTING] INFO a.jorje.lsp.impl.index.ApexIndexer - ApexIndexer: No indexing changes found
11:39:20.900 [ApexIndexer STARTING] INFO a.jorje.lsp.impl.index.ApexIndexer - ApexIndexer: StandardObjects: 2234
11:39:20.902 [ApexIndexer STARTING] INFO a.jorje.lsp.impl.index.ApexIndexer - ApexIndexer: CustomObjects: 501
11:39:20.902 [ApexIndexer STARTING] INFO a.jorje.lsp.impl.index.ApexIndexer - ApexIndexer: ApexFiles: 492
11:39:20.903 [ApexIndexer STARTING] INFO a.jorje.lsp.impl.index.ApexIndexer - ApexIndexer: ErrorFiles: 221
11:39:20.903 [ApexIndexer STARTING] INFO a.jorje.lsp.impl.index.ApexIndexer - ApexIndexer: Total Memory (MB): 612
11:39:20.903 [ApexIndexer STARTING] INFO a.jorje.lsp.impl.index.ApexIndexer - ApexIndexer: Used Memory (MB): 183
11:39:20.903 [ApexIndexer STARTING] INFO a.jorje.lsp.impl.index.ApexIndexer - ApexIndexer: Scanning user-defined types took 1041 ms.
11:39:20.906 [Apex Prelude Service STARTING] INFO a.j.l.i.s.ApexPreludeManagedService - Scanning built-in and system Apex types took 1957 ms.

I downgraded to v65.15.2 and its gone for now.

[dan9khoa]

Also happened to me and a co-worker recently.

Whenever this happens, I see in ActivityMonitor.app on Mac (or Task Manager on Windows) that the process called Code Helper (Plugin) runs with 100% CPU and it heats up the laptop.
I have to force stop this process, which in VS Code it would show the pop up saying "Aura Language Server crashed". So I think it's related to this. After stopping it, the file customlabels.d.ts would stop being open and the CPU is back to normal.
It happens everytime VS Code is opened.

The only thing that worked for me to stop this was to delete the metadata for Custom Labels CustomLabels.labels-meta.xml from VS Code.

[camisotro]

Yes, running into this on Windows too. Disabling Aura Language Server helped. Thankfully not working on any Aura today.

[madhur310]

Thanks for reporting the issue @justin-lyon @juanmtriguero @camisotro @dan9khoa. Are any of repositories that you are working on public? Can you point me to them so it can help debug the issue better.

[camisotro]

@madhur310 I am not working from any repository. Just a local project connected to a sandbox that has source tracking enabled.

[git2gus]

This issue has been linked to a new work item: W-21180077

[madhur310]

@justin-lyon @juanmtriguero @camisotro @dan9khoa could you help verify if the vsixes from https://github.com/forcedotcom/salesforcedx-vscode/actions/runs/21690084807?pr=6832 help resolve the issue on your end? After following the link, scroll down and you should see VS Code Extensions. Make sure to install all the vsixes and reload the vscode window once installed.

[justin-lyon]

The .sfdx folder is not commonly committed in public repos but I can create one that has it.

I tried reproducing in some other projects - but it only seems to impact projects that already have typings file, .sfdx/typings/lwc/customlabels.d.ts.

I tried creating a fresh project with a single customlabel (in force-app) in it but that doesn't seem to be enough to create the typings file.

What steps do I need to take to make sure that the typings file exists?

[madhur310]

@justin-lyon since you have a project that shows this issue, can you try installing the vsixes from the link in previous comment? Remember to install all the salesforce extensions from the folder and reload your vscode once you do. Let me know what behavior you see once installed.