Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Web and WebWorks Development

Reply
BlackBerry Development Advisor
tneil
Posts: 3,708
Registered: ‎10-16-2008
My Device: Z10
My Carrier: Rogers

Re: Memory leak using focused based navigation - test case included

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 :smileyhappy:

Tim Neil
Director, Application Platform & Tools Product Management
Follow me on Twitter
Please use plain text.
BlackBerry Development Advisor
tneil
Posts: 3,708
Registered: ‎10-16-2008
My Device: Z10
My Carrier: Rogers

Re: Memory leak using focused based navigation - test case included

Looking at the JavaScript for the navigation mode... I notice that we store all of the focusable elements in the "focusableNodes" array variable.. but I don't ever see us assign it to null or [ ].

 

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.

Tim Neil
Director, Application Platform & Tools Product Management
Follow me on Twitter
Please use plain text.
Regular Contributor
MLUY
Posts: 51
Registered: ‎07-20-2011
My Device: PlayBook
My Carrier: RIM

Re: Memory leak using focused based navigation - test case included

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

Please use plain text.
Regular Contributor
MLUY
Posts: 51
Registered: ‎07-20-2011
My Device: PlayBook
My Carrier: RIM

Re: Memory leak using focused based navigation - test case included

It's been a while... any progress? 

Please use plain text.
New Contributor
shanesmith
Posts: 7
Registered: ‎03-29-2012
My Device: Dev
My Carrier: Dev

Re: Memory leak using focused based navigation - test case included

For what it's worth, my (unscientific) tests confirm that this memory leak is still in the latest SDK 2.3.1.5. Removing that config option seems to resolve it. Also just to note that I'm using Sencha Touch 2.

Please use plain text.