Knockout memory leak

Question

Part of our application polls for updates, and then updates the model with the changes. It flows, most noticeably in chrome. I saw a problem in IE when I left an application that worked for a long period of time, but it is most noticeable in chrome (the chrome version is 19.0.1084.56 m).

Here is an example on jsFiddle http://jsfiddle.net/JApKE/9/ . Hit the refresh button over and over and you will see that the memory creeps up.

We use v2.1.0 (I saw in the previous question, someone said that there is a problem with the foreach bindings that were discussed in this version).

Any ideas?

Thanks Tom

Answer 1

I do not see a noticeable increase in memory usage, in any case this post can be useful, it is about how to effectively manage the observed array: http://www.knockmeout.net/2012/04/knockoutjs-performance-gotcha.html

Answer 2

After a multiple click, the memory will grow. but as soon as you get the garbage collector to collect memory, it will be freed.

You can start collecting by going to the Chrome Developer Tools timeline tab and clicking the arrow icon.