Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)
BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."
- Kevin Michaluk, Founder, CrackBerry.com
Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.
09-24-2011 07:12 AM - edited 09-24-2011 07:37 AM
Here is the video proof of the issue on OS5
We are professional development company and signed contract with customer who wants to run on OS 5. We trusted a SDK which has reached 2.x version but surprisingly seeing develpoment stuff do not aware of the issues clearly. I request the fix for OS 5.
if your priority focus is OS 6 will your company handle my contract compensation ?
09-24-2011 07:49 AM
Which version of the WebWorks SDK are you using. There were memory fixes in v2.1.1 that I believe also affected 5.0 devices. There were also a few APIs that were left over in the v2.1.1 release that were not found that are also now fixed in v2.2.
From your video I couldn't say conclusively that it is a memory issue that you are running into.. Are you using v2.1.1?
09-24-2011 07:52 AM
Some more questions...
Have you seen this issue both on the device and on the Simulator?
Which Device Model Number and os version eg. 5.0.0.x are you finding the issue on?
Is it possible for you to send us your application for us to test?
09-24-2011 07:56 AM - edited 09-24-2011 11:37 AM
Thanks for quick response, Both Eclipse Plugin and standalone v2.1.1.
Both in simulator real devices v184.108.40.2067 and more previous ones.
Source codes has sent directly to you.
09-24-2011 11:02 AM
Any chance you could Private Message me the source so that we can debug through the APIs that are being used.
09-26-2011 12:52 PM
As an update to unimedisys's reported problem on BB5 devices... our investigation with your app is showing that it doesn't look like a memory leak issue. Memory is being kept in check.. Which is good news
What appears to be happening is that eventually the OS throws an error around to many threads running in your application and that it can't create another thread.
We're disecting the code and looking for the root cause.
09-28-2011 09:16 AM
Please check out the following thread. We have been able to post up a pre-release version of the v2.2 SDK that has the memory fixes.
Details are in the post:
09-28-2011 01:37 PM