I have been able to track down all the memory leaks related to reloading a Store with new data. In my chrome memory profiles I didnt see the mentioned 6mb memory increase. For me it went up by 1.7mb after each refresh, which is still a lot, and I'm still looking to see if I can somehow bring this down a bit.

However, with the fixed I have made, when I keep refreshing the store with new data, the memory usage stays exactly the same which should solve the crashes you experienced.

I have slightly adjusted your test case to make it easier to refresh the store several times in a row without having to go back.

Also of note is that this override will slow down the setData call a bit, which is something I'm still working on resolving. Since we are properly removing and destroying every record from the Model cache, there is some extra logic involved with some suboptimal code branches. This will be better in the 2.0.1 release.