microsoft / microsoft/TypeScript

Memory skyrockets with VSCode extension

Open
#63,886 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
111k
Forks
14.3k
Avg merge
2d 4h
Merged PRs (30d)
132

Description

### Extension Version

0.20260708.2

### VS Code Version

1.133.0

### Operating system Version

Ubuntu 26.04

### Steps to reproduce

1. Setup a blank project and install these 3 packages
```
mkdir test-memory
cd test-memory
npm init -y
npm install gulp sass gulp-sass
```
2. Create a file `gulpfile.js` (or any name afaik) with the below contents
```js
"use strict";

const gulp = require("gulp");
const sass = require("sass");
const gulpSassPackage = require("gulp-sass");
// const gulpSass = gulpSassPackage(sass);
```
3. Open said file in VSCode with the Typescript 7 extension enabled
4. Open a memory monitor and uncomment the last line
5. Run `Restart TS Server` or `Reload window` after memory starts exploding to prevent full computer crash

### Issue

In the scenario outlined memory explodes to all remaining memory on my system within 5-10 seconds if I don't stop it.
I have no idea why this specific combination of factors causes this but it's incredibly consistent even in an isolated project as set up above. I have tested this with all my other extensions disabled, as long as the `Typescript 7` extension is enabled and `Enable tsgo` is on the memory explosion happens.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the report with the provided npm setup and gulpfile.js, then open it in VS Code with the TypeScript 7 extension and Enable tsgo enabled. Monitor memory while uncommenting the gulp-sass initialization and compare behavior after restarting the TS server or reloading the window. Done means the minimal reproduction no longer causes unbounded memory growth.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js, sass, typescript, vscode
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.