垃圾收集(GC)是通过删除不再需要的对象来自动进行内存管理的一种形式。

任何处理内存的进程都遵循以下步骤:

1 -分配你需要的内存空间

2 -做一些处理

3 -释放这个内存空间

有两种主要的算法用于检测哪些对象不再需要。

引用计数垃圾收集:该算法将“一个对象不再需要”的定义简化为“一个对象没有其他对象引用它”，如果没有引用点，该对象将被删除

标记扫描算法:将每个对象连接到根源。任何对象都不连接根或其他对象。该对象将被移除。

目前大多数现代浏览器使用第二种算法。

什么是JavaScript垃圾收集?

检查这个

对于web程序员来说，了解JavaScript垃圾收集的重要一点是， 为了写出更好的代码?

在Javascript中，你不关心内存分配和释放。整个问题都需要Javascript解释器来解决。在Javascript中泄漏仍然是可能的，但它们是解释器的错误。如果你对这个话题感兴趣，你可以阅读更多 www.memorymanagement.org

垃圾收集(GC)是通过删除不再需要的对象来自动进行内存管理的一种形式。

任何处理内存的进程都遵循以下步骤:

1 -分配你需要的内存空间

2 -做一些处理

3 -释放这个内存空间

有两种主要的算法用于检测哪些对象不再需要。

引用计数垃圾收集:该算法将“一个对象不再需要”的定义简化为“一个对象没有其他对象引用它”，如果没有引用点，该对象将被删除

标记扫描算法:将每个对象连接到根源。任何对象都不连接根或其他对象。该对象将被移除。

目前大多数现代浏览器使用第二种算法。

在计算机科学中，垃圾收集(GC)是自动内存管理的一种形式。垃圾收集器，或者仅仅是垃圾收集器，尝试回收垃圾或对象所使用的内存，这些对象将永远不会被应用程序再次访问或更改。”

所有JavaScript引擎都有自己的垃圾收集器，它们可能有所不同。大多数时候你不需要和他们打交道，因为他们只是在做他们应该做的事情。

写出更好的代码主要取决于你对编程原理、语言和特定实现的了解程度。

据我所知，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的下一次扫描删除该对象并释放其内存。

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完全不同。