在windows上，您可以使用Drip.exe来查找内存泄漏或检查您的free mem例程是否工作。

这真的很简单，只要输入一个网站的URL，你就会看到集成IE渲染器的内存消耗。然后点击刷新，如果内存增加，你在网页的某个地方发现了内存泄漏。但这也非常有用，看看释放内存的例程是否适用于IE。

当涉及到DOM对象时，要注意循环引用:

JavaScript中的内存泄漏模式

请记住，只有在没有对对象的活动引用时才能回收内存。这是闭包和事件处理程序的一个常见陷阱，因为一些JS引擎不会检查内部函数中实际引用了哪些变量，而只是保留封闭函数的所有局部变量。

这里有一个简单的例子:

function init() {
    var bigString = new Array(1000).join('xxx');
    var foo = document.getElementById('foo');
    foo.onclick = function() {
        // this might create a closure over `bigString`,
        // even if `bigString` isn't referenced anywhere!
    };
}

只要事件处理程序存在，简单的JS实现就不能收集bigString。有几种方法可以解决这个问题，例如在init()末尾设置bigString = null (delete对局部变量和函数参数不起作用:delete将从对象中删除属性，并且变量对象不可访问-如果您试图删除局部变量，ES5在严格模式下甚至会抛出ReferenceError !)

如果您关心内存消耗，我建议尽可能避免不必要的闭包。

据我所知，JavaScript的对象在没有对对象的引用时周期性地进行垃圾收集。这是自动发生的事情，但如果你想了解更多关于它是如何工作的，在c++级别，看一看WebKit或V8源代码是有意义的

Typically you don't need to think about it, however, in older browsers, like IE 5.5 and early versions of IE 6, and perhaps current versions, closures would create circular references that when unchecked would end up eating up memory. In the particular case that I mean about closures, it was when you added a JavaScript reference to a dom object, and an object to a DOM object that referred back to the JavaScript object. Basically it could never be collected, and would eventually cause the OS to become unstable in test apps that looped to create crashes. In practice these leaks are usually small, but to keep your code clean you should delete the JavaScript reference to the DOM object.

通常，使用delete关键字立即取消对JSON数据等大对象的引用是一个好主意，特别是在移动web开发中。这将导致GC的下一次扫描删除该对象并释放其内存。

在javascript中，垃圾收集是不确定的，对象何时会被清除，或者是否会被清除。这适用于强引用的对象。强引用对象不受垃圾回收的影响。

在ES12之后，可以执行以下实现来检查对象何时被垃圾收集。

要了解更多关于javascript垃圾收集的知识，你可以使用ES12之后可用的终结器。

let a = new Array(200).fill(true);

构造定稿器

const cleanup = new FinalizationRegistry(key => {
  // your code here
});

cleanup.register(a, 'wewew');

对象'a'现在不可达，终结器回调将在垃圾收集后发生

这句话摘自博客

DOM组件是“垃圾收集”的，JScript组件也是如此，这意味着如果您在任何一个组件中创建了一个对象，然后失去了对该对象的跟踪，它最终将被清除。

例如:

function makeABigObject() {
var bigArray = new Array(20000);
}

When you call that function, the JScript component creates an object (named bigArray) that is accessible within the function. As soon as the function returns, though, you "lose track" of bigArray because there's no way to refer to it anymore. Well, the JScript component realizes that you've lost track of it, and so bigArray is cleaned up--its memory is reclaimed. The same sort of thing works in the DOM component. If you say document.createElement('div'), or something similar, then the DOM component creates an object for you. Once you lose track of that object somehow, the DOM component will clean up the related.

Eric Lippert wrote a detailed blog post about this subject a while back (additionally comparing it to VBScript). More accurately, he wrote about JScript, which is Microsoft's own implementation of ECMAScript, although very similar to JavaScript. I would imagine that you can assume the vast majority of behaviour would be the same for the JavaScript engine of Internet Explorer. Of course, the implementation will vary from browser to browser, though I suspect you could take a number of the common principles and apply them to other browsers.

引自该页:

JScript uses a nongenerational mark-and-sweep garbage collector. It works like this: Every variable which is "in scope" is called a "scavenger". A scavenger may refer to a number, an object, a string, whatever. We maintain a list of scavengers -- variables are moved on to the scav list when they come into scope and off the scav list when they go out of scope. Every now and then the garbage collector runs. First it puts a "mark" on every object, variable, string, etc – all the memory tracked by the GC. (JScript uses the VARIANT data structure internally and there are plenty of extra unused bits in that structure, so we just set one of them.) Second, it clears the mark on the scavengers and the transitive closure of scavenger references. So if a scavenger object references a nonscavenger object then we clear the bits on the nonscavenger, and on everything that it refers to. (I am using the word "closure" in a different sense than in my earlier post.) At this point we know that all the memory still marked is allocated memory which cannot be reached by any path from any in-scope variable. All of those objects are instructed to tear themselves down, which destroys any circular references.

垃圾收集的主要目的是让程序员不必担心他们创建和使用的对象的内存管理问题，当然有时无法避免——至少对垃圾收集的工作方式有一个粗略的了解总是有益的。

历史注释:答案的早期修订对delete操作符的引用不正确。在JavaScript中，delete操作符从对象中删除一个属性，这与C/ c++中的delete完全不同。