JavaScript setInterval（）方法会导致内存泄漏吗？ [英] Does JavaScript setInterval() method cause memory leak?

问题描述

目前正在开发基于JavaScript的动画项目。

我注意到，正确使用 setInterval（） ， setTimeout（）甚至 requestAnimationFrame 在没有我的请求的情况下分配内存，并导致频繁的垃圾回收调用。更多GC调用=闪烁： - （

例如;当我在Google Chrome中调用init（）执行以下简单代码时，内存分配+垃圾收集在前20-30秒没问题...

  function init（）
 {
 var ref = window.setInterval（function（）{draw（）;}，50）; 
} 
 
 function draw（）
 {
 return true 
} 
  

不知何故，在一分钟左右的时间内，开始分配内存的奇怪增加！由于init（）仅被调用一次，分配内存大小增加的原因是什么？

（编辑：chrome screenshot已上传）

注意＃1：是的，我尝试在下一个setInterval（）之前调用clearInterval（）。问题仍然存在！

注意＃2：为了解决问题，我是保持上面的代码简单和愚蠢。

解决方案

编辑：

  function init（）
 {
 var ref = window.setInterval（function（ ）{draw（）;}，50）; 
} 
 function draw（）
 {
 console.log（'Hello'）; 
} 
 init（）; 
  

显然 setTimeout 和 setInterval 不是Javascript的正式部分（因此它们不是v8的一部分）。实施由实施者决定。我建议你看一下 setInterval的实现和例如在node.js

Currently developing a JavaScript based animation project.

I have noticed that, proper use of setInterval(), setTimeout() and even requestAnimationFrame allocates memory without my request, and causes frequent garbage collection calls. More GC calls = flickers :-(

For instance; when I execute the following simple code by calling init() in Google Chrome, memory allocation + garbage collection is fine for the first 20-30 seconds...

function init()
{
    var ref = window.setInterval(function() { draw(); }, 50);
}

function draw()
{
    return true
}

Somehow, within a minute or so, starts a strange increase in allocated memory! Since init() is called only for once, what is the reason for the increase in allocated memory size?

(Edit: chrome screenshot uploaded)

NOTE #1: Yes, I have tried calling clearInterval() before the next setInterval(). Problem remains the same!

NOTE #2: In order to isolate the problem, I'm keeping the above code simple and stupid.

解决方案

EDIT: Yury's answer is better.

---

tl;dr IMO there is no memory leak. The positive slope is simply the effect of setInterval and setTimeout. The garbage is collected, as seen by sawtooth patterns, meaning by definition there is no memory leak. (I think).

I'm not sure there is a way to work around this so-called "memory leak." In this case, "memory leak" is referring to each call to the setInterval function increasing the memory usage, as seen by the positive slopes in the memory profiler.

The reality is that there is no actual memory leak: the garbage collector is still able to collect the memory. Memory leak by definition "occurs when a computer program acquires memory but fails to release it back to the operating system."

As shown by the memory profiles below, memory leak is not occurring. The memory usage is increasing with each function call. The OP expects that because this is the same function being called over and over, there should be no memory increase. However, this is not the case. Memory is consumed with each function call. Eventually, the garbage is collected, creating the sawtooth pattern.

I've explored several ways of rearranging the intervals, and they all lead to the same sawtooth pattern (although some attempts lead to garbage collection never happening as references were retained).

function doIt() {
    console.log("hai")
}

function a() {
    doIt();
    setTimeout(b, 50);
}
function b() {
    doIt();
    setTimeout(a, 50);
}

a();

http://fiddle.jshell.net/QNRSK/14/

function b() {
    var a = setInterval(function() {
        console.log("Hello");
        clearInterval(a);
        b();                
    }, 50);
}
b();

http://fiddle.jshell.net/QNRSK/17/

function init()
{
    var ref = window.setInterval(function() { draw(); }, 50);
}
function draw()
{
    console.log('Hello');
}
init();

http://fiddle.jshell.net/QNRSK/20/

function init()
{
    window.ref = window.setInterval(function() { draw(); }, 50);
}
function draw()
{
    console.log('Hello');
    clearInterval(window.ref);
    init();
}
init();​

http://fiddle.jshell.net/QNRSK/21/

Apparently setTimeout and setInterval are not officially parts of Javascript (hence they are not a part of v8). The implementation is left up to the implementer. I suggest you take a look at the implementation of setInterval and such in node.js

这篇关于JavaScript setInterval（）方法会导致内存泄漏吗？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！