02-13-2012 05:59 PM
Just to triple check..... using v2.3 didn't help your issue?
I know the dev support said that they were still able to reproduce.. but I wanted to make sure that you tried it and it didn't help.
I want to make sure I don't chase down a rabit hole
02-13-2012 06:10 PM
We do re-assign it on scroll with a new array.. but I'm wondering if re-assigning it will pass the old array items to the garbage collection, or if it will simply hold those old array items in memory somewhere.
I'm going to double check on this one.
02-13-2012 06:13 PM
I haven't tested that myself. The devsupport guy did a really good job, and I had neither the time nor any reason to double check his statement. Perhaps you may check with him directly
03-29-2012 05:10 PM
For what it's worth, my (unscientific) tests confirm that this memory leak is still in the latest SDK 18.104.22.168. Removing that config option seems to resolve it. Also just to note that I'm using Sencha Touch 2.