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.
11-05-2012 08:02 AM
Hi, we have an application out in the field that terminates unexpectedly. It is usually at the same point but not always. It is very random when it happens and no matter how hard we try cannot re-produce in house. It seems to be mainly on 9360 7.1 devices.
Can anyone offer any help on what causes a webworks app to terminate unexpectedly? No errors or exceptions (code is in a try / catch) are experienced.
11-05-2012 09:08 AM
Without having much information about the app, the only thing that comes to mind is perhaps something is happening that's causing a memory leak. Generally, the app will shutdown at the same point though, when the event that causes the memory issues runs.
11-05-2012 10:33 AM
Thanks for the response Chad. Now begs the question 'what causes a memory leak? !!!
The routine is basically is looping through the DOM to pick out entered information, saving it to local storage and then fireing it back via XHR. It never seems to hit the XHR when it fails, so either it's bombing out when accesing the DOM or when writing to local storage.