Language service crashes

Which @angular/* package(s) are the source of the bug?

language-service

Is this a regression?

Yes

Description

I have problems with the new version of the angular language service extension for VSCode.
I have only this extension running.
When i want to see all references VSCode indicates loading, which takes around 1-2 minutes.
I tried different versions of the extension, this issue first appeared with version 20.3.3.

Please provide a link to a minimal reproduction of the bug

No response

Please provide the exception or error you saw

<--- Last few GCs --->

[58405:0x24800158000]    64415 ms: Scavenge (during sweeping) 3970.3 (3995.0) -> 3956.7 (3996.0) MB, pooled: 0.0 MB, 10.89 / 0.00 ms (average mu = 0.266, current mu = 0.254) allocation failure; 
[58405:0x24800158000]    70665 ms: Mark-Compact (reduce) 3957.9 (3996.0) -> 3941.5 (3965.0) MB, pooled: 0.0 MB, 5586.49 / 0.00 ms (+ 89.3 ms in 20 steps since start of marking, biggest step 5.0 ms, walltime since start of marking 5702 ms) (average mu = 0.
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

[Info  - 15:11:45] Connection to server got closed. Server will restart.
[Error - 15:11:45] Request textDocument/codeLens failed.
Error: Connection got disposed.
	at Object.dispose (/home/myname/.vscode/extensions/angular.ng-template-21.0.0/index.js:4665:25)
	at Object.dispose (/home/myname/.vscode/extensions/angular.ng-template-21.0.0/index.js:9450:35)
	at LanguageClient.handleConnectionClosed (/home/myname/.vscode/extensions/angular.ng-template-21.0.0/index.js:11658:38)
	at LanguageClient.handleConnectionClosed (/home/myname/.vscode/extensions/angular.ng-template-21.0.0/index.js:14102:15)
	at closeHandler (/home/myname/.vscode/extensions/angular.ng-template-21.0.0/index.js:11646:16)
	at CallbackList.invoke (/home/myname/.vscode/extensions/angular.ng-template-21.0.0/index.js:2769:35)
	at _Emitter.fire (/home/myname/.vscode/extensions/angular.ng-template-21.0.0/index.js:2828:34)
	at closeHandler (/home/myname/.vscode/extensions/angular.ng-template-21.0.0/index.js:3927:24)
	at CallbackList.invoke (/home/myname/.vscode/extensions/angular.ng-template-21.0.0/index.js:2769:35)
	at _Emitter.fire (/home/myname/.vscode/extensions/angular.ng-template-21.0.0/index.js:2828:34)
	at IPCMessageReader.fireClose (/home/myname/.vscode/extensions/angular.ng-template-21.0.0/index.js:2970:27)
	at ChildProcess.<anonymous> (/home/myname/.vscode/extensions/angular.ng-template-21.0.0/index.js:4914:45)
	at ChildProcess.emit (node:events:531:35)
	at maybeClose (node:internal/child_process:1101:16)
	at Socket.<anonymous> (node:internal/child_process:456:11)
	at Socket.emit (node:events:519:28)
	at Pipe.<anonymous> (node:net:346:12)
[Error - 15:11:45] Request textDocument/codeLens failed.
Error: Connection got disposed.
	at Object.dispose (/home/myname/.vscode/extensions/angular.ng-template-21.0.0/index.js:4665:25)
	at Object.dispose (/home/myname/.vscode/extensions/angular.ng-template-21.0.0/index.js:9450:35)
	at LanguageClient.handleConnectionClosed (/home/myname/.vscode/extensions/angular.ng-template-21.0.0/index.js:11658:38)
	at LanguageClient.handleConnectionClosed (/home/myname/.vscode/extensions/angular.ng-template-21.0.0/index.js:14102:15)
	at closeHandler (/home/myname/.vscode/extensions/angular.ng-template-21.0.0/index.js:11646:16)
	at CallbackList.invoke (/home/myname/.vscode/extensions/angular.ng-template-21.0.0/index.js:2769:35)
	at _Emitter.fire (/home/myname/.vscode/extensions/angular.ng-template-21.0.0/index.js:2828:34)
	at closeHandler (/home/myname/.vscode/extensions/angular.ng-template-21.0.0/index.js:3927:24)
	at CallbackList.invoke (/home/myname/.vscode/extensions/angular.ng-template-21.0.0/index.js:2769:35)
	at _Emitter.fire (/home/myname/.vscode/extensions/angular.ng-template-21.0.0/index.js:2828:34)
	at IPCMessageReader.fireClose (/home/myname/.vscode/extensions/angular.ng-template-21.0.0/index.js:2970:27)
	at ChildProcess.<anonymous> (/home/myname/.vscode/extensions/angular.ng-template-21.0.0/index.js:4914:45)
	at ChildProcess.emit (node:events:531:35)
	at maybeClose (node:internal/child_process:1101:16)
	at Socket.<anonymous> (node:internal/child_process:456:11)
	at Socket.emit (node:events:519:28)
	at Pipe.<anonymous> (node:net:346:12)
[Info  - 15:11:46] Angular language server process ID: 59590
[Info  - 15:11:46] Imported typescript/lib/tsserverlibrary is version 5.9.3.
[Info  - 15:11:46] Using @angular/language-service v21.0.0-rc.3 from /home/myname/.vscode/extensions/angular.ng-template-21.0.0/node_modules/@angular/language-service/index.js
[Info  - 15:11:46] Logging is turned off. To enable, run command 'Open Angular server log'.
[Info  - 15:11:49] Enabling language service for /home/myname/git/myproj/proj/frontend/tsconfig.json.

Please provide the environment you discovered this bug in (run `ng version`)

"@angular/cli": "~19.1.7",
"@angular/compiler-cli": "^19.1.6",
"@angular/animations": "^19.1.6",
"@angular/cdk": "^19.1.4",
"@angular/common": "^19.1.6",
"@angular/compiler": "^19.1.6",
"@angular/core": "^19.1.6",
"@angular/forms": "^19.1.6",
"@angular/platform-browser": "^19.1.6",
"@angular/platform-browser-dynamic": "^19.1.6",
"@angular/router": "^19.1.6",
NodeVersion: v23.6.0,
"typescript": "~5.7.3",
 OS: TUXEDO OS x86_64
VSCoder: 1.106.1

Anything else?

No response

@JeanMeche

@JeanMeche
should be a potential help wanted, GFI and area: vscode labels

should be a potential help wanted, GFI

Really? Do you know what the issue is? Good first issues are ones with clear solutions and I do not see that here.

I tried different versions of the extension, this issue first appeared with version 20.3.3.

That’s unfortunate. 20.3.3 was the first successful release from this repository. We’re now effectively past the point of no return with the v21 release.

I don't think there’s enough information here to begin to investigate a fix

Furthermore, since version 20.3.1 I cannot Ctrl+Click on a reference in an HTML file to jump to the declaration in the component.ts file.
Again no other extensions where enabled.

/home/felix_rieg/.vscode/extensions/angular.ng-template-20.3.1/server/index.js:294
      throw new Error(`Failed to resolve '${packageName}' with minimum version '${minVersion}' from ` + JSON.stringify(probeLocations, null, 2));
      ^

Error: Failed to resolve 'typescript/lib/tsserverlibrary' with minimum version '5.0' from [
  "/home/felix_rieg/.vscode/extensions/angular.ng-template-20.3.1",
  "/home/felix_rieg/git/myProj/proj"
]
    at resolveWithMinVersion (/home/felix_rieg/.vscode/extensions/angular.ng-template-20.3.1/server/index.js:294:13)
    at resolveTsServer (/home/felix_rieg/.vscode/extensions/angular.ng-template-20.3.1/server/index.js:308:14)
    at requireOverride (/home/felix_rieg/.vscode/extensions/angular.ng-template-20.3.1/server/index.js:361:57)
    at Object.<anonymous> (/home/felix_rieg/.vscode/extensions/angular.ng-template-20.3.1/server/index.js:248101:25)
    at Module._compile (node:internal/modules/cjs/loader:1714:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1848:10)
    at Module.load (node:internal/modules/cjs/loader:1448:32)
    at Module._load (node:internal/modules/cjs/loader:1270:12)
    at c._load (node:electron/js2c/node_init:2:17993)
    at TracingChannel.traceSync (node:diagnostics_channel:322:14)

Node.js v22.20.0
[Info  - 17:08:33] Connection to server got closed. Server will restart.
/home/felix_rieg/.vscode/extensions/angular.ng-template-20.3.1/server/index.js:294
      throw new Error(`Failed to resolve '${packageName}' with minimum version '${minVersion}' from ` + JSON.stringify(probeLocations, null, 2));
      ^

20.3.1 and 20.3.2 were broken releases. Any bugs in those versions don’t quite mean anything

Are you able to narrow things down to a smaller reproduction that you can share as a GitHub repo? Can you try deleting code from your project to pinpoint the areas that might be the source of the issue? Without being to reproduce this ourselves, we won’t be able to find a fix.

I can try to reproduce it after work. However, I've found that the language service only works when I open VSCode directly in a frontend folder.

Our project structure has multiple frontend applications:

root/frontendOne
root/frontendTwo

When I open VSCode at the root level, the Angular language service doesn't work properly. However, if I open VSCode directly in frontendOne or frontendTwo, everything works fine.

This worked correctly in version 20.3.0, but broke in later versions.

Looks like we didn't get a repro/follow-up, we'll close this issue for now. Feel free to file a new issue if you can provide a repro.

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}

Navigation Menu

Repository navigation

Language service crashes #65356

Which @angular/* package(s) are the source of the bug?

Is this a regression?

Description

Please provide a link to a minimal reproduction of the bug

Please provide the exception or error you saw

Please provide the environment you discovered this bug in (run `ng version`)

Anything else?

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Language service crashes #65356

Description

Which @angular/* package(s) are the source of the bug?

Is this a regression?

Description

Please provide a link to a minimal reproduction of the bug

Please provide the exception or error you saw

Please provide the environment you discovered this bug in (run ng version)

Anything else?

Activity

aparzi commented on Nov 19, 2025

atscott commented on Nov 19, 2025

felixrieg commented on Nov 19, 2025

atscott commented on Nov 19, 2025

atscott commented on Nov 19, 2025

felixrieg commented on Nov 20, 2025

JeanMeche commented on Feb 10, 2026

angular-automatic-lock-bot commented on Mar 13, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Please provide the environment you discovered this bug in (run `ng version`)