01-24-2012 06:45 PM
I just built my app with SDK 2.3, certainly seems better than the older version. The hourglass is gone, it's more seamless. It still does give a out of memory error after a while. Here is the notes from 2.3 release:
How will your memory be managed better?
In BlackBerry WebWorks for Smartphones SDK v2.2, we introduced a “memory maid” that handled cleaning up after some memory leaks related to callbacks being held by the native Java® layer. The maid would, under certain conditions, trigger a Java garbage collection. In this version, we are fine-tuning the logic the memory maid uses in order to make this process less intrusive to the end user and will result in fewer hourglasses, especially the fairly prevalent one that happens immediately on load of some applications.
01-26-2012 08:36 AM - edited 01-26-2012 08:37 AM
I have the same problem. I just built my app with SDK 2.3 and using focus based navigation, but It still does give a out of memory error after a while.
When will BlackBerry solution to the problem.
We need solution yet
Please help us quickly
01-26-2012 10:22 AM
@kiranmobile, @rperez, how is your application architected? Do you have multiple pages that you navigate through? Do you use divs that are hidden and shown depending on user navigation requests? These approaches will lead to leaks and can result in low memory errors.
We recommend an approach of loading new pages off-DOM using Ajax, and then switching the content. This is very quick and provides a much better environment for memory use. I am currently trying to get a "tutorial" type blog post on this together...
01-27-2012 01:11 PM - edited 01-27-2012 03:47 PM