Memory leakage occurs in the getTypeAtLocation method in the latest version.

[majie77]

Acknowledgement

• I acknowledge that issues using this template may be closed without further explanation at the maintainer's discretion.

Comment

Invoke the getTypeAtLocation method one million times cyclically. Before and after the loop, perform GC and print heapUsed. The memory usage increases by about 150 MB.

[jakebailey]

You haven't provided much information.

Are you calling it on the same location each time, or a different one?

How much memory is being used before/after?

If you're saying it happens in the "latest" version, are you saying that it didn't used to happen?

If it didn't happen before, have you tried to bisect with https://www.npmjs.com/package/every-ts?

[majie77]

My demo code is as follows:

global.gc();
const m = process.memoryUsage();
console.log(m.heapUsed);
for (let a=1;a <= 1000000;a++) {
typeChecker.getTypeAtLocation(node.typeName);
}
global.gc();
const m1 = process.memoryUsage();
console.log(m1.heapUsed);

Test results of different versions：

[RyanCavanaugh]

Please post a sample we can run ourselves; this could depend on any number of factors