You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With both "IntelliSense for CSS class names" and "Angular Language Service" enabled, following happened.
Starting VS Code in a pretty basic test project spawns a VSC process that continues to increase memory consumption at 10-13% CPU load (i7-6800K) ultimately resulting in ALS repoting "JavaScript heap out of memory".
Closing VS Code does not kill the process, but leaves it running at CPU load and memory fluctuating around 2-3 GB.
Disabling Angular Language Service makes everything else work.
Disabling IntelliSense for CSS class names makes everything else work.
When adding IntelliSense for CSS class names, the output for ALS shows Search path: c:/1work/Programming/angular2/routing-start/node_modules/clone
Full ALS log with IntelliSense for CSS class names (autocomplete/intellisense never works for anything)
With both "IntelliSense for CSS class names" and "Angular Language Service" enabled, following happened.
Starting VS Code in a pretty basic test project spawns a VSC process that continues to increase memory consumption at 10-13% CPU load (i7-6800K) ultimately resulting in ALS repoting "JavaScript heap out of memory".
Closing VS Code does not kill the process, but leaves it running at CPU load and memory fluctuating around 2-3 GB.
Disabling Angular Language Service makes everything else work.
Disabling IntelliSense for CSS class names makes everything else work.
When adding IntelliSense for CSS class names, the output for ALS shows
Search path: c:/1work/Programming/angular2/routing-start/node_modules/clone
Full ALS log with IntelliSense for CSS class names (autocomplete/intellisense never works for anything)
Full ALS log without IntelliSense for CSS class names (autocomplete/intellisense works at startup)
Note that, there is an similar issue breaking the Polymer/vscode-plugin, so the "fault" is probably in here.
The text was updated successfully, but these errors were encountered: