Javascript: memory leak with loop?

Question

I've got a simple loop that creates and destroys (hopefully) empty objects: http://jsfiddle.net/TgWze/

function Test()
{
}

function generate()
{
    for(var i = 0; 1000 > i; ++i)
    {
        var view = new Test();

        delete view;
    }
}

The memory profile in Chrome/Safari shows memory-leak like behavior if I keep clicking the link: http://cl.ly/BnCV

Am I missing something?

Besides a possible memory leak, 'delete' is redundant since the reference will be out of scope after one loop anyway. — Dykam
– Dykam, Commented Nov 14, 2011 at 19:00
You can't actually use delete like that; it's only for deleting properties in an object. — pimvdb
– pimvdb, Commented Nov 14, 2011 at 19:01
I stand corrected (too much perl lately), I meant to say that old view-variable would be out of scope in the next loop by redefinition. — Dykam
– Dykam, Commented Nov 14, 2011 at 19:15
Who keeps sending developers stuck with an manual-memory-management mindset to program in GC'd languages? — user395760
– user395760, Commented Nov 14, 2011 at 19:24

SLaks · Accepted Answer · 2011-11-14 19:00:24Z

3

That looks like normal GC behavior. Once there are too many objects, the GC cleans them up.

It would only be a memory leak if the troughs after each peak (just after the GC runs) get successively higher, indicating that the GC didn't catch everything.

answered Nov 14, 2011 at 19:00

SLaks

891k182 gold badges1.9k silver badges2k bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Joe · Accepted Answer · 2011-11-14 19:07:17Z

3

It's managed memory. So it will collect the deleted object at some point when the garbage collector runs. You deleting the objects actually doesn't do anything. However since, view is never reference, it should be collected easily.

edited Nov 14, 2011 at 19:07

answered Nov 14, 2011 at 19:00

Joe

82.8k18 gold badges130 silver badges147 bronze badges

2 Comments

Sam Over a year ago

so, the key point here is that the object will be deleted next time Garbage Collector is run. This is conceptually different from C++ new/delete and that is the reason I see raise of the memory in profiler, b/c link is clicked too often and then, there is a drop in memory, which is due to garbage collector run. Thanks.

Joe Over a year ago

Exactly, although new does allocate some memory; delete does not deallocate it

Vlad A. Ionescu · Accepted Answer · 2012-08-06 14:32:31Z

0

That code does not leak.

To convince yourself you can take snapshots of the memory and compare before and after. Have a look at this guide that I wrote, for more details: http://www.vladalexandruionescu.com/2012/08/javascript-memory-leaks.html.

answered Aug 6, 2012 at 14:32

Vlad A. Ionescu

2,7981 gold badge18 silver badges19 bronze badges

Collectives™ on Stack Overflow

Javascript: memory leak with loop?

3 Answers 3

Comments

2 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

2 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related